-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Failed to container restore
a container which name is equal to a image name
#15055
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Nice catch, @sstosh! Podman should probably try looking up the container if the image has failed. If both fail, both errors should returned. |
I would also say if there is a match for both we should prefer the container. |
SGTM. If that fails, try an image. |
sstosh
added a commit
to sstosh/podman
that referenced
this issue
Jul 26, 2022
If there is a match for both container and image, we restore the container. Fixes: containers#15055 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
sstosh
added a commit
to sstosh/podman
that referenced
this issue
Jul 26, 2022
If there is a match for both container and image, we restore the container. Fixes: containers#15055 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
sstosh
added a commit
to sstosh/podman
that referenced
this issue
Jul 27, 2022
If there is a match for both container and image, we restore the container. Fixes: containers#15055 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 10, 2022
If there is a match for both container and image, we restore the container. Fixes: containers#15055 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 10, 2022
If there is a match for both container and image, we restore the container. Fixes: containers#15055 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Related to #13505
If a container name is equal to a image name, failed to restore the container.
The reason is that
image
has a higher search priority thancontainer
.I don't know what this priority is correct.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
If a container name is NOT equal to a image name, succeed to restore the container.
Output of
podman version
:Output of
podman info --debug
:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora36, KVM
The text was updated successfully, but these errors were encountered: