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

Error: read-only image store assigns the same name to multiple images #119

Open
wahabk opened this issue Oct 29, 2024 · 2 comments
Open
Labels
bug Something isn't working
Milestone

Comments

@wahabk
Copy link

wahabk commented Oct 29, 2024

Hello! We have ran into this issue:

$ podman-hpc images
Error: read-only image store assigns the same name to multiple images
$ podman-hpc image ls
REPOSITORY                            TAG         IMAGE ID      CREATED      SIZE
<IMAGE_NAME>  v1.3        7589b976db7f  2 weeks ago  15 GB
$ podman-hpc images
Error: read-only image store assigns the same name to multiple images
$ podman-hpc ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
[no running containers]

The only similar issue I could find is:

https://bugzilla.redhat.com/show_bug.cgi?id=1952637

I checked the images.json and layers.json on the login and compute nodes and I found no duplicates. We had to remove the entire overlay* directories and start from scratch.

Have you ran into this before? Or know of methods to debug this?

@scanon
Copy link
Member

scanon commented Dec 4, 2024

Yes. I think we have a fix for this. The issue I believe was collisions in the name history field that wasn't being managed. I need to check on the status of that fix.

@scanon scanon added this to the Release 1.1.1 milestone Dec 4, 2024
@scanon scanon added the bug Something isn't working label Dec 5, 2024
@moustakas
Copy link

In case it's helpful, I'm also seeing the same issue intermittently---but not reproducibly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants