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
Hi.
I have recently switched to Fedora CoreOS for my projects.
This is my third installation of NPM, and docker-compose file is mostly unchanged, apart from adding :z to mounts, which is required if you have SE Linux enabled.
I'm running into a strange problem that i don't know how to debug.
NPM periodically (at random) stops responding to http(s) requests.
Docker shows that container is running, and container log only shows that everything has started and ready for connections.
The moment i do "docker-compose up -d", and it says that it is already up to date, everything works again.
Which way do i look to resolve this?
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
-
Hi.
I have recently switched to Fedora CoreOS for my projects.
This is my third installation of NPM, and docker-compose file is mostly unchanged, apart from adding :z to mounts, which is required if you have SE Linux enabled.
I'm running into a strange problem that i don't know how to debug.
NPM periodically (at random) stops responding to http(s) requests.
Docker shows that container is running, and container log only shows that everything has started and ready for connections.
The moment i do "docker-compose up -d", and it says that it is already up to date, everything works again.
Which way do i look to resolve this?
Beta Was this translation helpful? Give feedback.
All reactions