Connectivity issues between containers on the same network on Debian-based DietPi

I’ve updated docker-ce to 27.3.1 on my dietpi linux today.
after that I saw a lot of connection issues between the containers.
the container lost the connection but have been able to reconnect after a few seconds.

I’ve downgraded to 27.2.0 and there I don’t have this issue. all container have a stable connection to each others.

any idea’s what this could be?

all containers have the same bridge network

You could check the release notes (link).

I would also add that Dietpi linux is not a supported distribution. Supported distributions can be found here:

https://docs.docker.com/engine/install/#supported-platforms

If dietpi had a guide for installing Docker, maybe you can try a Dietpi form (if it exists) just in case it is not a general Docker issue.

Dietpi is based on Debian and uses the standard packages.
And I had the same issue as well on raspberry

I found the topic you opend on the Dietpi forum so I leave the link here:

A distribution is made to change some things in the base distribution. Any small change could affect how some software work which was not expected running on that distribution even if using the same packages.

I’m not saying you can’t ask about the issue here, but if it can’t be reproduced on Debian, it will be harder to help you. I use Ubuntu, and I didn’t notice network issues there yet with v27.3.1. So it is either something that happens on Debian, or something that is different on your machine.

What does this command returns on Dietpi?

cat /etc/os-release

I think the only network related change according to the changelog is this:

I still have no solution, but I found something.
Is it possible, that two containers can have the same internal mac address?
In my case two containers have the same mac address. not sure if this is a problem, but it might be

I changed the mac address from one of this containers and it seems that solved the issue.

A mac address should be unique in a network, otherwise the switches and network devices in this network will freak out… Regardless, whether docker is part of the equation or not.

yes, I know.
but how can it be that two containers get the same mac address? they are both on the same network.

If you don’t specify the mac addresses, docker should assign unique mac addresses.

I haven’t specified any mac address. but two containers got the same mac. only removing one from the network and adding it back solved the issue

Sounds like a bug to me…

If you have troubleshooting notes that allow to reconstruct the issue, then it would be great if you could report it here https://github.com/moby/moby/issues.

I tried to reproduce. But it happened only twice.

I can now reproduce it. it happens after docker deamon restart
I opened a bug

1 Like

It seems you are indeed not the first with this issue

1 Like