When Docker stops a container, it also stops the associated logging, and hence the window is closed because there is no longer real-time monitoring possible. Opening the log of a stopped container just shows what has been stored, but is not updated in real-time and the user is asked to close the window at their convenience.
When Docker stops a container, it also stops the associated logging, and hence the window is closed because there is no longer real-time monitoring possible. Opening the log of a stopped container just shows what has been stored, but is not updated in real-time and the user is asked to close the window at their convenience.
ok I figured out what you guys meant above, this is user error... sort of. I had "--restart unless-stopped" in the extra options field.
So as a medium level user of docker, I would like to ask that either a pull down be added to adjust the docker restart option so its more obvious or to disable the autoclose of the log window... a warning at the bottom saying "Due to this container restarting, This log will not update unless it is closed and re-opened" would be fine and more user friendly I would think.
also my fix has been to change the extra parameters to "--restart on-failure:3" that way it will auto-restart but will only try 3x so I can still check the log when its a real failure.(this is for a Authenticator docker so its important to stay up, and it likes to randomely crash once a month or so)
as this auto closing log prevents me from seeing what my docker container is crashing at...ITS A BUG!
Or its designed to make us go crazy and find another solution for our nas systems...but i digress
You can post now and register later.
If you have an account,
sign in now
to post with your account.
Note:
Your post will require moderator approval before it will be visible.