I'm on 6.12.6. I ran into some problems that led to an unclean shutdown. I got some advice here to fix the problems, and followed those steps (switched from macvlan to ipvlan, recreated the custom docker network (same name "proxynet") and recreated the docker image. But now my docker containers (Swag and Nextcloud) aren't connecting to proxynet. Host access to custom networks is enabled, as is Preserve user defined networks.

 

Searching a bit on the forum there did seem to be some cases of problems with custom docker networks not working after an unclean shutdown and possibly the Host access to custom networks setting being shown as enabled when in fact it had not been enabled. The suggested solution was to disable and re-enable this setting, which seemed to work in some cases.

 

I've tried that, also rebooted and tried that again, and I still have the same problem. Here's what I have:

 

root@Tower:~# docker network ls
NETWORK ID     NAME       DRIVER    SCOPE
bd5116d783dc   br0        ipvlan    local
a3b3aaa3ce56   bridge     bridge    local
83cf0e1b1ef5   host       host      local
9e74c89874cb   none       null      local
69ed37939ece   proxynet   bridge    local
root@Tower:~# 

 

So it looks like proxynet is running?

 

There was also a suggestion that the problem was caused by a race condition, where the docker container tried to connect to the custom network before the network was up. I tested that as well by restarting Swag, same problem. Then also tested by setting Swag autostart to off, disabling docker service, re-enabling docker service, waiting a few minutes and then starting Swag. Still had the same problem.

 

Any suggestions on how to fix this?

tower-diagnostics-20240331-2100.zip

I tried deleting and then recreating proxynet, but that didn't help. Then I tried creating a new network, proxynet2. I assigned my Swag and Nextcloud containers to it and they seemed to be OK. Then I reassigned the containers back to proxynet and lo and behold, they're now working.

 

To tidy up I deleted proxynet2. So far, so good.

 

If things run fine for a few days, I'll mark this as solved.