August 23, 20205 yr I've been using Unraid for a few years now, and I'm very happy with it. But there is one thing that frustrates me every time I have to reboot (which admittedly isn't often, but my power was out this morning for longer than my UPS could handle...) I have a bunch of Docker containers set up, a few of which need to be directly connected to my local network (in other words, they have their own IP on my LAN). I currently achieve this by connecting them to the automatically generated macvlan network, and everything's great. The trouble is, after a reboot, those containers can't start automatically because they "remember" which network to connect to by its ID rather than its name, and when Unraid stops/starts the docker service, it deletes and recreates that network. So after every reboot I have to go delete and recreate the containers that use it. I know Unraid can preserve user-defined networks across reboots, so my first thought was to simply manually create my own network and use that, but docker won't let you create two macvlan networks that have the same parent interface. So that's a no-go. I tried searching around in the forums and found some comments that implied that people had created multiple macvlan networks, but it was never the main topic of discussion, so it was never explained how they'd done it. I'm pretty much out of ideas, but today's power outage was enough to reignite my interest in finding a solution. Anyone have any ideas for how I could make reboots less painful?
Archived
This topic is now archived and is closed to further replies.