-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix network connect race with docker-compose #10654
Conversation
@mheon PTAL |
Network connect/disconnect has to call the cni plugins when the network namespace is already configured. This is the case for `ContainerStateRunning` and `ContainerStateCreated`. This is important otherwise the network is not attached to this network namespace and libpod will throw errors like `network inspection mismatch...` This problem happened when using `docker-compose up` in attached mode. Signed-off-by: Paul Holzinger <[email protected]>
Good catch, LGTM |
You caught a flake: Been seeing this one a lot, I suspect we'll have to chase this down next week (CC @edsantiago) Restarted |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
Network connect/disconnect has to call the cni plugins when the network
namespace is already configured. This is the case for
ContainerStateRunning
and
ContainerStateCreated
. This is important otherwise the network isnot attached to this network namespace and libpod will throw errors like
network inspection mismatch...
This problem happened when usingdocker-compose up
in attached mode.