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
Had an issue today when new docker containers were not accessible after startup. After a bit of poking around, I saw that the /etc/nginx/conf.d/default.conf file only held servers that had already started. No new containers were being added.
I stopped, removed and started a new proxy container, and all is well in the world again. New docker containers are appearing in the upstream list
Has anyone seen this behaviour before ? I know that it will be incredibly difficult to try and fix seeing as I have no further information, but just wanted to raise this just in case someone else has had the problem and has a fix / solution / comment to make
thanks
julian
The text was updated successfully, but these errors were encountered:
I've seen it w/ docker-gen several months ago but not recently w/ newer versions of docker. There was an issue in docker related to lost events but I'm not sure what the status of it is anymore.
Had an issue today when new docker containers were not accessible after startup. After a bit of poking around, I saw that the /etc/nginx/conf.d/default.conf file only held servers that had already started. No new containers were being added.
I stopped, removed and started a new proxy container, and all is well in the world again. New docker containers are appearing in the upstream list
Has anyone seen this behaviour before ? I know that it will be incredibly difficult to try and fix seeing as I have no further information, but just wanted to raise this just in case someone else has had the problem and has a fix / solution / comment to make
thanks
julian
The text was updated successfully, but these errors were encountered: