Docker Community Forums

Share and learn in the Docker community.

Docker and network.service

Hello everyone,

I had an issue today with a container. I resolved it but I’d like to know the exact reason to it.
It might be more a Linux question than a Docker one, but they are linked :smiley: so …

Here is the issue I had :

After a long time without touching the container, it was running correctly. One of my team needed to change some stuff on the network layer of the server and he did a network.service restart. Then, the application can’t connect to the database it uses, and of course stoppde working. So I need to restart the docker service to make it works. I suppose it get some network parameters or something liek this that are mandatory for docker.

The question is what’s happen on the server network layer, when a network.service restart happens that it’s not “forwarded” to the docker network layer. I guess it has to be linked to the docker0 bridge.

Thanks in advance.

Regards :smiley:

You can create user-defined overlay networks using docker network create , in the same way that you can create user-defined bridge networks. Services or containers can be connected to more than one network at a time. Services or containers can only communicate across networks they are each connected to.