dziekon

For anyone struggling with Docker connectivity issues on latest Arbian minimal images, I've found solution (although, can't say if it's a good or bad solution, I'm not a sysops wizard or whatever) which does seem to work fine for my use case. Tested on "Armbian_community 24.8.0-trunk.399 Bookworm with Linux 6.6.36-current-sunxi64" By following this stackoverflow answer (https://stackoverflow.com/a/76440642/951007), I've modified netplan's default configuration file (currently "/etc/netplan/10-dhcp-all-interfaces.yaml" file) from: (...) all-eth-interfaces: match: name: '*' (...) to (...) all-eth-interfaces: match: name: 'en*' (...) and restarted the entire SBC. With this change applied, docker network adapters changed their SETUP from "configuring" to "unmanaged", as it apparently should be in the first place (although please do note that other adapters have been changed as well, so proceed with caution): $ sudo networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 end0 ether routable configured 3 wlan0 wlan off unmanaged 4 docker0 bridge no-carrier unmanaged 5 br-xxxxxxxxxxxx bridge no-carrier unmanaged 6 br-xxxxxxxxxxxy bridge no-carrier unmanaged After that, Docker was able to communicate with the outside world: $ docker run busybox ping -c 1 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=57 time=4.741 ms (...) and was able to communicate with other docker-based services in the same network - in my case, a Spoolman instance was not able to communicate with Postgresql instance started using one docker compose file. --- Again, please do note that I'm no expert in this regard, so if you decide to follow this solution, I would recommend verifying whether other services (that require connectivity in any way) still work as expected.