Skip to content
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

Merged
merged 1 commit into from
Jun 12, 2021

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Jun 11, 2021

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 11, 2021
@Luap99
Copy link
Member Author

Luap99 commented Jun 11, 2021

@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]>
@mheon
Copy link
Member

mheon commented Jun 11, 2021

Good catch, LGTM

@mheon
Copy link
Member

mheon commented Jun 11, 2021

You caught a flake:
[Fail] Podman search [It] podman search attempts HTTP if registry is in registries.insecure and force secure is false

Been seeing this one a lot, I suspect we'll have to chase this down next week (CC @edsantiago)

Restarted

@Luap99 Luap99 mentioned this pull request Jun 11, 2021
@rhatdan
Copy link
Member

rhatdan commented Jun 11, 2021

/approve
/lgtm
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 11, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 11, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 11, 2021

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rhatdan
Copy link
Member

rhatdan commented Jun 12, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 12, 2021
@openshift-merge-robot openshift-merge-robot merged commit d1cb5d1 into containers:master Jun 12, 2021
@Luap99 Luap99 deleted the net-connect branch June 12, 2021 11:40
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants