May 23May 23 Hello,I have several docker containers that piggyback off my binhex-delugevpn container's network. This has worked for years, but it seems after I updated to 7.2.6 (And 7.2.7 after updating this morning) those dependent containers that use the "--net=container:binhex-delugevpn" parameter no longer start after a server reboot. The delugevpn container starts up no problem and is first in the boot order, I've also put delays on the other dependent containers and moved them all the way down the list to ensure it isn't a timing issue. The gotcha here is that I cannot even start these containers manually. When doing so I get a "Bad Parameter" error.Oddly enough all I have to do is edit each container, add a space in the container name and then erase the space in the name (or make any change really, just something to make the "Apply" button become active). After clicking apply the container will start.Any help here would be appreciated.
May 23May 23 Community Expert Solution Any reason you don't just select "Container" as the network type and select the container you are networking too?
May 23May 23 Author 2 hours ago, MowMdown said:Any reason you don't just select "Container" as the network type and select the container you are networking too?Yes.... A very good reason. Because I'm ignorant...Thank you friend! This seems to have fixed the issue!
Join the conversation
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.