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 for compatibility volume creation #7804

Merged
merged 1 commit into from
Sep 28, 2020

Conversation

baude
Copy link
Member

@baude baude commented Sep 28, 2020

in the compatibility layer, creating a volume with a name that already does not result in an error. instead a 201 response with the existing volume's information is returned. while it seems like a bug on the part of docker and they agree, no attempt has been made to fix it in five years. See moby/moby#16068

Fixes: #7740

Signed-off-by: baude bbaude@redhat.com

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: baude

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 28, 2020
@baude baude force-pushed the issue7740 branch 2 times, most recently from e2b4368 to 4cace31 Compare September 28, 2020 18:18
@psgreco
Copy link

psgreco commented Sep 28, 2020

Just tested and this solves #7740 for me

@rhatdan
Copy link
Member

rhatdan commented Sep 28, 2020

I love bug for bug compatibility.

in the compatibility layer, creating a volume with a name that already does not result in an error.  instead a 201 response with the existing volume's information is returned. while it seems like a bug on the part of docker and they agree, no attempt has been made to fix it in five years.  See moby/moby#16068

Fixes: containers#7740

Signed-off-by: baude <bbaude@redhat.com>
@jwhonce
Copy link
Member

jwhonce commented Sep 28, 2020

LGTM

@TomSweeneyRedHat
Copy link
Member

LGTM
assuming happy tests

@rhatdan
Copy link
Member

rhatdan commented Sep 28, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 28, 2020
@QiWang19
Copy link
Contributor

/lgtm

@openshift-merge-robot openshift-merge-robot merged commit 6b803a6 into containers:master Sep 28, 2020
@baude baude deleted the issue7740 branch May 18, 2022 15:19
@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 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 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.

podman/docker compatibility during volume creation
8 participants