Never seen this before. I have 3 servers, most running Unraid since 6.9 or so. All have multiple interfaces with some interfaces having VLANs. Each runs macvlan, with bridging off on all interfaces. I assign the appropriate subinterface and a static IP for each container. Two have stayed pretty current on 6.12.x and went from 6.12.6 to 6.12.8 just fine.
One 11th gen Intel has stayed on 6.11.5 because 6.12 was causing instability. I decided to bite the bullet and try 6.12.8 and for the first time ever the upgrade has removed my two custom networks (bond2.60 and eth4.70) from the containers. Actually the ones on eth4.70 show that on the Docker screen and the others reverted to None. Regardless, when I click into them to select the Network type the only options listed are the standard Bridge, Host, and None options. Docker settings still shows the custom networks just as they should and have.
Diagnostics attached. Reverting to 6.11.5 left the jacked up "None" items, but at least I can select the custom networks as I should. As it stands I have no path to upgrade beyond 6.11.5 for this server. FWIW, I tried ipvlan and that didn't help. Until I'm clearer on the security and visibility implications of macvlan and ipvlan I'd like to stay on the former unless the instability returns.
UPDATE - removing diagnostics now for some security hygiene and the fact that that it's been some time so I finally recreated all the server and docker network stuff from scratch.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.