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

run --rmi : image not known #23719

Closed
edsantiago opened this issue Aug 22, 2024 · 0 comments · Fixed by #23767
Closed

run --rmi : image not known #23719

edsantiago opened this issue Aug 22, 2024 · 0 comments · Fixed by #23767
Assignees
Labels
flakes Flakes from Continuous Integration remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

[+0064s] not ok 60 [030] podman run --rmi in 2092ms
...
<+065ms> # # podman-remote --url unix:///tmp/CI_XMpA/podman_tmp_qXfw rm /c_t60-jg6dl4n1
<+059ms> # c_t60-jg6dl4n1
         #
<+011ms> # # podman-remote --url unix:///tmp/CI_XMpA/podman_tmp_qXfw run --rmi quay.io/libpod/testimage:00000004 /bin/true
<+411ms> # time="2024-08-20T17:05:58-05:00" level=warning msg="quay.io/libpod/testimage:00000004: image not known"
x x x x x x
sys(2) remote(2) rawhide(1) root(2) host(2) sqlite(2)
debian-13(1)
@edsantiago edsantiago added flakes Flakes from Continuous Integration remote Problem is in podman-remote labels Aug 22, 2024
@Luap99 Luap99 assigned Luap99 and unassigned mheon Aug 27, 2024
Luap99 added a commit to Luap99/libpod that referenced this issue Aug 27, 2024
Since commit 458ba5a the cleanup process now removes the image as
well, thus the removal is racy and it will cause an error here.

The code tried to ignore the errorwith errors.Is() but this never works
across the remote API. However the API already has a ignore option so
juts use that and fix the error message so that we can easly find the
root cause and I do not have to guess where the log was written.

Fixes containers#23719

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99 added a commit to Luap99/libpod that referenced this issue Aug 27, 2024
Since commit 458ba5a the cleanup process now removes the image as
well, thus the removal is racy and it will cause an error here.

The code tried to ignore the error with errors.Is() but this never works
across the remote API. However the API already has a ignore option so
juts use that and fix the error message so that we can easily find the
root cause and I do not have to guess where the log was written.

Fixes containers#23719

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
TomSweeneyRedHat pushed a commit to TomSweeneyRedHat/podman that referenced this issue Oct 14, 2024
Since commit 458ba5a the cleanup process now removes the image as
well, thus the removal is racy and it will cause an error here.

The code tried to ignore the error with errors.Is() but this never works
across the remote API. However the API already has a ignore option so
juts use that and fix the error message so that we can easily find the
root cause and I do not have to guess where the log was written.

Fixes containers#23719

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
(cherry picked from commit 8e78028)
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakes Flakes from Continuous Integration remote Problem is in podman-remote
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants