Custom VLANs work, but eth0, eth3 are unavailable. I've gone through all the settings I'm aware of trying to figure out what's going on and find nothing; nor anything in the release notes that obviously points to what's going on here. Will have to roll back if there's not a quick fix someone can help point me to.

Available options:

Bridge

Host

Container

None

Custom : eth0.4

Custom : eth0.5

List of interfaces defined in Docker config:

Attaching diagnostics.

diagnostics-20251031-1450.zip

Even more bizarre - my backup server (which I updated first, but doesn't typically run dockers) still presents eth0 etc as available interfaces for Docker!

I've cross-checked network and docker settings and they're the same except there are no VLANs on the backup server at the moment... testing whether adding one breaks this.

I can not repro this issue on the backup machine. I've added VLANs as well as ipv4+ipv6 and can still choose from among the custom networks including eth0 and eth0.5 when defining docker config.

Edited October 31, 2025Oct 31 by _cjd_

Should also note, syslog shows that docker can not find these interfaces. I've tried removing them and re-adding them in the docker settings.

I've also now discovered a share (/Music) which regressed to very old configuration, but had a weird copy .cfg in the flash /config/shares folder. Was able to fix that with some renaming.

docker.cfg in /config has very wrong data, it's still trying to enable bond1 eth0_4 and eth0_5, and I can't figure out where it's getting that. There is no bond1. Can't manually edit this? I tried to update the list manually and it regressed soon as I restarted the docker service. Still trying to figure out a solution.

Completely removing all networks for docker config, then re-adding them all has brought eth3 back, but still not eth0.

Also, I can no longer connect to SMB shares... That was working after the update, but possibly broke with me twiddling share config files to fix the messed up one? edit: solved, I had renamed the bogus share config to a non .cfg extension and it seems that caused issues; removing it and shares are all working again.

Edited October 31, 2025Oct 31 by _cjd_

Your diagnostics indicate you have 2 networks in docker settings that don't exist in you Unraid network settings.

• 192.168.3.0/24

• 192.168.20.0/24

Remove old entries from your docker network settings, or add these additional networks into Unraid network settings.

The must exist in both places.

@tjb_altf4 Those are VLANs eth0.4 and eth0.5 and are working. And they show in network settings attached to eth0.

I did also already completely remove all docker network assignments and re-add them, which caused eth3 to become available for docker, noted above.

I will approach from the network side and completely redo all of that though, first again removing everything from docker. I just am at a loss where random bogus config (possibly just old? That's my hypothesis here, it's all old config; the share issue certainly was) could appear as a result of the upgrade.

I have now completely rebuilt network and docker configs (deleted the two network configs, the one docker config) and rebuilt.

eth0 remains unavailable to docker.

eth0.4 and eth0.5 are VLANs on eth0. They are defined in network settings and enabled in docker configs. They are working.

eth1 (previously eth3) is available and working.

I tried adding a VLAN for the eth0 network (it's VLAN1) in network settings and docker configs, and it also does not show up as available.

I am going to try renaming eth0 to eth10 or something to see if there's hiding configurations somewhere I don't know about, but I am quite out of ideas and increasingly frustrated. This should not be misbehaving like this. edit: this did not help.

Edited November 1, 2025Nov 1 by _cjd_

On the chance it's helpful, current diagnostics.

I have worked around eth0 not being available - two services I was able to shift to bridge and the other I had to move to eth1 for now - this unblocks most use cases while we try to figure this out and/or I completely redesign my network around this.

diagnostics-20251101-1548.zip

No luck still. I've attempted to vacate the vlans, added new nics, removed them... No eth0.

In the end I need the vlans for my setup so they're in olave (attached to eth0). Work-around functional but not preferred.

Any suggestions on what I might try next?