-
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
podman/docker compatibility during volume creation #7740
Comments
Do you think this is a bug in Docker? Does not see proper to not return an error when something already exists. I checked their man page and it does not mention this behaviour? |
The man page of |
Sure, but you could make the arguments about creating a directory. mkdir /tmp What happens in Docker if I change the options?
This really feels like a bug in docker. |
Does |
The behaviour is inconsistent. |
By any chance could you open an issue with Docker on this to get their opinion. |
So Docker seem to be of the opinion that this behavior is not good and should be changed... Given that, I think we should document the difference and leave it, in the expectation that Docker will eventually change it. |
@rsommer Interested in opening a PR to transfer.md? |
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 <[email protected]>
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 <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When a named volume is created via docker and the volume does already exist, no error ist returned. podman on the other hand returns
Error: volume with name test already exists: volume already exists
Steps to reproduce the issue:
docker:
podman:
Describe the results you received:
podman throws an error when the volume does already exist.
Describe the results you expected:
podman just "returns" the existing volume, being compatible to docker. The behaviour was discovered while trying to replace the docker daemon in gitlab ci. The cache volumes used by the gitlab runner are (re-)created using the same volume name, leading to the shown error.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: