Conflicting IP address for containers

I have experienced a few rare times containers not being able to access each other via the default bridge network. Some of the times that happened when we were experiencing heat issues and problems on the network interface in hot days and related to Thermal Operating Range of BalenaFin

The latest time (during a heat event), some of the containers were assigned the same ip address by internal dns resolver. This is the log I could obtain (anonymized the container names):

root@ef4b243:~# balena ps -q | xargs -n 1 balena inspect --format ‘{{ .Name }} {{range .NetworkSettings.Networks}} {{.IPAddress}}{{end}}’ | sed ‘s#^/##’;
a____2409535_1428871 172.18.0.8
b____2409534_1428871 172.18.0.3
c____2409532_1428871 172.18.0.9
d____2409540_1428871 172.18.0.10
e____2409533_1428871 172.18.0.7
f____2409538_1428871 172.18.0.3
g____2409546_1428871 172.18.0.4
h____2409544_1428871
i_____2409547_1428871
j_____2409536_1428871 172.18.0.6
k____2409531_1428871 172.18.0.5
l____2409542_1428871 172.18.0.2
resin_supervisor

This was making container a not be able to reach container b

After restarting container f , it worked. No errors happened after that and I could not yet reproduce the error.

The containers that experience the conflict are using the default bridge (no network_mode configuration)

Is this a known issue? Is there a configuration that could avoid these conflicts to happen?

After the restart of container f, it got a new different IP address.

Hello, did this IP conflict occur after an update?

No update was performed.
I could not reproduce the error yet. If I get it again I will update this topic.

Hi, when you are able to reproduce this again can you notify us again so we can take a look please in the device?