January 22, 20251 yr Hello all! I'm just starting out with UnRaid and it's been a blast so far. There's so many resources and information available out there. The community is amazing! I am running into some issues here and there. I created a custom docker network using the commands 'docker network create'. It worked however, when I set a docker to use that network (say Plex), it wont map to a 192.168.x.x address. In tutorials and guides, I see it gets mapped to a 192.168.x.x which is what I would expect. I'm also on 7.0 stable. How can I have it map propperly? Edited January 22, 20251 yr by thedigitaldevil Additional info
January 22, 20251 yr Author Solution So I was able to resolve my previous issue by creating a docker network using the following and specifying a subnet that didn't overlap with an existing one. docker network create -d macvlan \ --subnet=10.0.1.0/24 \ --gateway=10.0.1.1 \ -o parent=bond0 \ dockernet After setting a docker to use this network, I got another error when starting up the container... Docker: Error response from daemon: failed to create the ipvlan port: device or resource busy Update... I followed the documentation here https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces and was able to get the private doicker network setup. I'm have further issues accessing the web gui of any container within that network. I'm going to make a separate post on that since the title to this one is misreprenting the issue. That, and I've had no reply. Edited January 23, 20251 yr by thedigitaldevil Update
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.