Balena Containers leaving Bridge network

Hello @klutchell we updated our development devices, we did not update the production devices, we do not take lightly the update of core software like Balena Supervisor without lots of testing.

  • Our devices reboot every 15 days by design.
  • Our devices reboot in case of critical failure of a service.
  • A container perform network management tasks (network interfaces) but just when needed.
  • It’s always the same containers the ones that lose the bridge network. We only have host-networking containers and bridge-networked containers the bridge ones are the ones that lose it.
  • The thread is not entirely about this, but something similar happens on this thread → DNS failure not caught by supervisor - #50 by alexgg
  • About sda, yes there is something to solve there, but I do not think is related to this issue. sda is an external device.

About persistent logging, we would have to enable in all our devices, because it’s something that does not happen all the time… I’ll enable on a few to see if I can capture.

Regards