You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Few days ago our Verdaccio hosted on internal Windows Server with Docker started to stops the running container.
Don't remember right now what version of Verdaccio that was, I updated it today to latest one hoping this will solve the issue.
After some investigation I got that, the container stops with status Exited (137).
It doesn't look like this is caused by out of memory, because docker inspect shows: "OOMKilled": false,
I tried many different levels in config for logging purposes (debug, trace, info etc) and I can't get any errors to show up
I have no idea what else can I do to track this issue? This is our company internal repository and everytime someone executes npm i, Verdaccio is going to abyss.
This Verdaccio instance is available through reverse proxy with following config (don't know, maybe some errors are hidden due to it?):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Few days ago our Verdaccio hosted on internal Windows Server with Docker started to stops the running container.
Don't remember right now what version of Verdaccio that was, I updated it today to latest one hoping this will solve the issue.
After some investigation I got that, the container stops with status Exited (137).
It doesn't look like this is caused by out of memory, because docker inspect shows: "OOMKilled": false,
I tried many different levels in config for logging purposes (debug, trace, info etc) and I can't get any errors to show up
I have no idea what else can I do to track this issue? This is our company internal repository and everytime someone executes npm i, Verdaccio is going to abyss.
This Verdaccio instance is available through reverse proxy with following config (don't know, maybe some errors are hidden due to it?):
Full docker inspect result:
Beta Was this translation helpful? Give feedback.
All reactions