I’ve been trying to place my container direclty on my local network. I’ve tried setting up MACVLAN and by using a docker-machine but I’ve been unable to communicate directly to the container.
Here is what I’ve done…
- Created a “macvlan” network named “LOCAL” and gave it the subnet from my local LAN. NOTE: I tied using the name of my local NIC for the parent interface but it always failed. I could only get the below command to be accepted by using “eth0”. Is this correct? What name is Docker expecting here?
docker network create -d macvlan LOCAL --subnet=192.168.0.0/24 --gateway=192.168.0.1 -o parent=eth0
- Ran an image, named it “SONARR”, attached it to the newly created “LOCAL” network and gave it an IP from the “LOCAL” subnet.
docker run --name=SONARR --net=LOCAL --ip=192.168.0.100 linuxserver/sonarr
- Adjusted “MobyLinuxVM” virtual switch to use an “external” network that ties direclty to my PC’s NIC.
Once this is complete I’m unable to communicate with the container at 192.168.0.100. I have a packet-capture running and do not see any packets whatsoever coming from 192.168.0.100.
Any ideas what I’m doing wrong? Does “MACVLAN” work on Windows 10? Should I be using a “docker-machine” instead?
Thanks for any help you can give!