You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to spin up my containers with nomad without need of a docker0 bridge, or need of NAT to expose my services.
docker supports --net=host, which spin up the container sharing the host network namespace.
that means containers will bind ports using the host network stack. this should simplify a lot for using in production environments, where we don't want to use overlay networks and rocket sciences.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I'd like to spin up my containers with nomad without need of a docker0 bridge, or need of NAT to expose my services.
docker supports --net=host, which spin up the container sharing the host network namespace.
that means containers will bind ports using the host network stack. this should simplify a lot for using in production environments, where we don't want to use overlay networks and rocket sciences.
The text was updated successfully, but these errors were encountered: