Bridge Network Interface On Virtual VM/Container On Linux Host Howto
by danmartinj from LinuxQuestions.org on (#5K5X1)
Hello,
I have a requirement where I want to deploy a custom OS quickly to another host OS to any one of our assets across a large network in general. Due to the practical use case it is important to expose the network interface to the routable internal network.
Due to the lower level details we originally thought Docker would be perfect for the job. So we built a custom image and started to deploy it remotely to other assets. The problem now is it actually seems to be quit more complex to bridge a docker container network interface to the host network. Obviously, we can do NAT/port mapping but that does not fit our specific use case as it causes various limitations. To bridge docker container network interface we tried this resource:
https://serverfault.com/questions/95...iginal-network
But, this did not quit work and since we were working remotely we actually locked ourselves out of the asset. After much pain we are starting to think maybe we should just go with KVM as a next possible solution.
However, I am not just wondering if maybe there is another way to bridge a docker container network interface to a host network? Or maybe KVM or something similar is the way to go instead of docker?
Any comments or advice could be really useful.
Thanks,
Joe
I have a requirement where I want to deploy a custom OS quickly to another host OS to any one of our assets across a large network in general. Due to the practical use case it is important to expose the network interface to the routable internal network.
Due to the lower level details we originally thought Docker would be perfect for the job. So we built a custom image and started to deploy it remotely to other assets. The problem now is it actually seems to be quit more complex to bridge a docker container network interface to the host network. Obviously, we can do NAT/port mapping but that does not fit our specific use case as it causes various limitations. To bridge docker container network interface we tried this resource:
https://serverfault.com/questions/95...iginal-network
But, this did not quit work and since we were working remotely we actually locked ourselves out of the asset. After much pain we are starting to think maybe we should just go with KVM as a next possible solution.
However, I am not just wondering if maybe there is another way to bridge a docker container network interface to a host network? Or maybe KVM or something similar is the way to go instead of docker?
Any comments or advice could be really useful.
Thanks,
Joe