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'm raising this incase anyone else has a similar problem.
I am using the two containers named as follows:
openvpn-server
openvpn-ui
I have a problem whereby if I don't set the containers to automatically restart when they fail using a docker restart policy, then the UI Restart server button just kills the container. I noticed after writing this that soe of the other events that trigger a conditional restart do seem to work. That said I'm manually rstarting containers as I work stuff out, so I might be masking some unexpected behaviors.
I don't quite know how to fix this, but looking in the restart.sh script I see that it is looking for a container names openvpn and not openvpn-server. It would seem that for this to work, then the naming of containers is very prescriptive.
It would be lovely if there were a way for the container to be restarted regardless of it's name, but I dont know how that might be accomplished.
Perhaps a suitable interim measure would be for the naming convention to be consistently applied to container naming as to image naming, and so hae the script look for openvpn-server.
Thanks
The text was updated successfully, but these errors were encountered:
HI, I'm raising this incase anyone else has a similar problem.
I am using the two containers named as follows:
I have a problem whereby if I don't set the containers to automatically restart when they fail using a docker restart policy, then the UI Restart server button just kills the container. I noticed after writing this that soe of the other events that trigger a conditional restart do seem to work. That said I'm manually rstarting containers as I work stuff out, so I might be masking some unexpected behaviors.
I don't quite know how to fix this, but looking in the restart.sh script I see that it is looking for a container names
openvpn
and notopenvpn-server
. It would seem that for this to work, then the naming of containers is very prescriptive.It would be lovely if there were a way for the container to be restarted regardless of it's name, but I dont know how that might be accomplished.
Perhaps a suitable interim measure would be for the naming convention to be consistently applied to container naming as to image naming, and so hae the script look for
openvpn-server
.Thanks
The text was updated successfully, but these errors were encountered: