-
Notifications
You must be signed in to change notification settings - Fork 59
Networking: "docker run --net=host ..." does not work. #81
Comments
--net=host will require mapping of the full host networking stack into the VM. This is currently not possible given the nature of VMs. Currently looking at the use cases of --net=host in container orchestrators and the plan it to support the use case vs supporting --net=host at this point in time. |
Reusing the host network stack doesn't really map to the VM model. Closing for now with the limitation documented in the wiki. Might want to revisit this if we find something using it and can partially implement it. |
@dlespiau @mcastelino @jodh-intel Question on this (before I maybe re-open this or create a new issue). I tried this on native hardware (connected over SSH), and SSH'd into a VM (ciao-down) - both times the effect is 'machine has hung', whereas I suspect reality is that 'machine has been taken off network'. Do we think we can at least add some code to realise when we are on the host network and fail more graciously? I had a quick peek at the code - my only thought on how is maybe we can detect that we are not in a network namespace (I don't even know if that is true for |
A new issue to try and detect that case sounds good to me (on both 2.x and 3.0 maybe). What exactly we can do then is interesting as well, ranging from failing to create the container to trying to bridging the VM to ethernet interfaces on the host. Something along the lines of detecting if we are in a networking ns sounds like the only thing we can really do indeed. |
Known limitation of code used to fix #38.
The text was updated successfully, but these errors were encountered: