I'm a home user, not a trained networking expert. I use Docker to run a few containers of use, mostly as a hobby. I like running docker containers for my simple app needs, as there are a lot of containers for various uses and trying them out isn't hard, but in some cases I'd rather they acted more like VMs: showing up as separate machines on the network.
In the past I've made use of a Macvlan network to have some of my containers get their own IP on the network but it suffered from two problems:
First, the docker server was handing out those IPs instead of just having them ask the router. I was able to make this work, but it wasn't optimal.
Second, Macvlans as a feature isolate the host, so I wasn't able to get any containers on the Macvlan network to see and interact with anything on the same physical device, only other things on the network. I've heard there are ways around this, but they aren't well documented or explained, and some have warnings that cinema hd it's ephemeral, it will need to be done again any time the machine reboots.
I'm wondering if there are ways of addressing these issues that are within my more limited abilities? Like, can I simply define the network for the Macvlan as being my whole network and tell it to use my router as the gateway instead of the docker server, effectively telling it to ask my router for an IP? Is there actually an easy to understand guide to making a permanent bridge between the macvlans and the host system? Does using ipvlan instead of Macvlan solve some of this?
In the past I've made use of a Macvlan network to have some of my containers get their own IP on the network but it suffered from two problems:
First, the docker server was handing out those IPs instead of just having them ask the router. I was able to make this work, but it wasn't optimal.
Second, Macvlans as a feature isolate the host, so I wasn't able to get any containers on the Macvlan network to see and interact with anything on the same physical device, only other things on the network. I've heard there are ways around this, but they aren't well documented or explained, and some have warnings that cinema hd it's ephemeral, it will need to be done again any time the machine reboots.
I'm wondering if there are ways of addressing these issues that are within my more limited abilities? Like, can I simply define the network for the Macvlan as being my whole network and tell it to use my router as the gateway instead of the docker server, effectively telling it to ask my router for an IP? Is there actually an easy to understand guide to making a permanent bridge between the macvlans and the host system? Does using ipvlan instead of Macvlan solve some of this?
Last edited: