For context I am working in a multi tenant server which means I encounter file permission errors frequently, i’m not sure if contributes to my issue though. So going into my problem, my docker containers suddenly stopped being able to communicate with each other. There all on the same custom network, and hence I take advantage of the automatic DNS. I can confirm communication works by using ping, which successfully transmits packets. I then confirmed that containers weren’t able to access each others ports that they were listening to by using nc -zv alias port
. I receive a connection timed out error. The odd part is that I am able to access the ports from the host to the container from python, but not from container to container. I am open to all suggestions. Thank you.
I have tried restarting the docker engine, restarting the containers, disconnecting from networks, reconnecting, and also creating new networks. The problem still persists. That is, I receive connection timed out errors.
This is my network config:
[
{
"Name": "my-network",
"Id": "unique-id",
"Created": "2024-08-01T20:54:28.217013318-04:00",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "172.20.0.0/16",
"Gateway": "172.20.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"container-id-1": {
"Name": "container-1",
"EndpointID": "endpoint-id-1",
"MacAddress": "xx:xx:xx:xx:xx:xx",
"IPv4Address": "172.20.0.2/16",
"IPv6Address": ""
},
"container-id-2": {
"Name": "container-2",
"EndpointID": "endpoint-id-2",
"MacAddress": "xx:xx:xx:xx:xx:xx",
"IPv4Address": "172.20.0.4/16",
"IPv6Address": ""
},
"container-id-3": {
"Name": "container-3",
"EndpointID": "endpoint-id-3",
"MacAddress": "xx:xx:xx:xx:xx:xx",
"IPv4Address": "172.20.0.3/16",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {}
}
]
MiguelBBeats is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.