-
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 pull prints the extra image ID when set additionalimagestores #18647
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
rhatdan
added a commit
to rhatdan/common
that referenced
this issue
May 26, 2023
Currently if you setup additional stores and pull the same image that exists in additionalstore, podman ends up reporting the ID twice. Fixes: containers/podman#18647 Signed-off-by: Daniel J Walsh <[email protected]>
rhatdan
added a commit
to rhatdan/common
that referenced
this issue
Jun 12, 2023
Currently if you setup additional stores and pull the same image that exists in additionalstore, podman ends up reporting the ID twice. Fixes: containers/podman#18647 Signed-off-by: Daniel J Walsh <[email protected]>
@rhatdan one way to test this in podman might be: @test ...
local imstore=$PODMAN_TMPDIR/imagestore
local sconf=$PODMAN_TMPDIR/storage.conf
cat >$sconf <<EOF
[storage]
driver="overlay"
[storage.options]
additionalimagestores = [ "$imstore" ]
EOF
# Or maybe save/load, to avoid network flakes?
run_podman pull -q --root $imstore $IMAGE
env CONTAINERS_STORAGE_CONF=$sconf run_podman images -a
# FIXME: confirming that it includes two copies of $IMAGE, one R/O false & one true, left as exercise for the reader
env CONTAINERS_STORAGE_CONF=$sconf podman pull -q $IMAGE
# FIXME: output should be exactly one line, only one line
} |
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 14, 2023
Fixes: containers#18647 Signed-off-by: Daniel J Walsh <[email protected]>
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 12, 2023
rhatdan
added a commit
to rhatdan/common
that referenced
this issue
Feb 5, 2024
Currently if you setup additional stores and pull the same image that exists in additionalstore, podman ends up reporting the ID twice. Fixes: containers/podman#18647 Signed-off-by: Daniel J Walsh <[email protected]>
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.
Issue Description
podman pull prints the extra image ID when set additionalimagestores.
Steps to reproduce the issue
Steps to reproduce the issue
# podman pull ubi9
Describe the results you received
Describe the results you expected
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
If additionalimagestore is added, the extra image ID is also printed additionally.
The text was updated successfully, but these errors were encountered: