thedigitaldevil
Members
-
Joined
-
Last visited
Solutions
-
thedigitaldevil's post in Docker Network Won't Map to a LAN IP:Port was marked as the answerSo 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.