May 2May 2 After upgrading to version 7.2.5 Unraid fails to start some containers. Here is an example:docker start binhex-sabnzbd Error response from daemon: failed to set up container networking: container sharing network namespace with another container or host cannot be connected to any other network failed to start containers: binhex-sabnzbdNote that this only happens for containers that I have routed through a VPN container with the --net=container:<YOUR_CONTAINER_NAME>.What should I do? I still want to use VPN for the container.
May 2May 2 Author I assume this has to with Unraid 7.2.5 upgrading Docker to version 29, but I am not sure.Seems like there might be two solutions here.Solution 1: Use container networksSet the network type to Container and use the container that has VPN as the "Container Network". In this case you don't have to use --net=container:<YOUR_CONTAINER_NAME>Solution 2: Remove port mappingsRemove all port mappings from the routed container. Add those ports to the VPN container instead. For example: add SABnzbd’s 8080 WebUI port to the VPN container and remove the port from the SABnzbd container. Make sure not to use The important part is that the routed container must not have both --net=container:<VPN_CONTAINER_NAME> together with any Docker network attachment or port publishing.
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.