September 13, 20223 yr I’ve set up several containers to use a mcvlan nework. Now I have the issue, that all containers which are setup with portainer stacks can't find the network after a reboot (network xxx not found). It doesn’t matter if I setup the mcvlan only within portainer or with the UNRAID gui for network and docker. The only different is, that the mcvlan which was setup within portainer is gone after restart. Only the config for the mcvlan is still present. The mcvlan whitch was setup only with the UNRAID gui comes back after a restart (but with a new networkID) If I setup the containers not with portainer stacks or the compose plugin, just with the UNRAID gui for new Containers, the containers can automaticly restart after a reboot - so they find the network. But this is for containers with a lot of variables a pain. The docker settings option “PRESERVE USER DEFINED NETWORKS” is always on. Is this a bug or a misunderstanding feature ?
September 15, 20223 yr Author Thanks for this. It's more a workaround, but it works 👍 I think its a bug that only this kind of mcvlan-setup works with stacks/compose and the preserve option.
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.