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
When we add a persistent route to our host route table, we noticed that the container also inherits these routes as well.
Expected behavior
The windows containers should be isolated from these persistent routes.
Information
Windows Version:
Docker Desktop Version: 4.0.1
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: Azure VM
This is reproducible issue.
We added extra network configuration by adding a persistent route from the container host of the default docker nat bridge to connect with the instance metadata service endpoint. When running the windows container, the windows container inherits the host route table.
Why does the window containers inherit the host route table for persistent routes? Are there any downsides of taking a dependency on this behavior?
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale
Actual behavior
When we add a persistent route to our host route table, we noticed that the container also inherits these routes as well.
Expected behavior
The windows containers should be isolated from these persistent routes.
Information
This is reproducible issue.
We added extra network configuration by adding a persistent route from the container host of the default docker nat bridge to connect with the instance metadata service endpoint. When running the windows container, the windows container inherits the host route table.
Why does the window containers inherit the host route table for persistent routes? Are there any downsides of taking a dependency on this behavior?
Steps to reproduce the behavior
No Persistent Routes Added
Container Route Table with no persistent route
Added Persistent Route
Container Route Table with persistent route
The text was updated successfully, but these errors were encountered: