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
Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running] #11487
Comments
@vrothberg PTAL. This does go down into c/storage, though, so I'll tag @nalind as well. |
I have never seen that happening. The layer store is lock-protected. @arottigni-te, can you share an exact reproducer (i.e., the exact commands) if possible? |
At the point where store.Layers() calls lstore.Layers() (store.go:3047 in podman 3.2.3 corresponds to store.go:3060 in the containers/storage main branch), the lock is not held. |
Ouch ... sounds like it should be held? |
Yes, we should probably be acquiring a read lock on the store before reading its layers list. |
Make sure that the layer store is locked when loading the layers. Reported-in: github.com/containers/podman/issues/11487 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Make sure that the layer store is locked when loading the layers. Reported-in: github.com/containers/podman/issues/11487 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
The fix merged into c/storage (containers/storage#1014) and will make it into Podman 3.4. |
thanks :) |
Any chance this could make it into Podman 3.3? :) |
Not upstream. In case you're using an enterprise Linux (e.g., RHEL or SLES), please open a bug there to trigger request backports. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I'm creating and removing containers frequently using the podman's REST api. Sometimes creating a container fails with the following error:
Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running]
This is for podman 3.2.3 on ubuntu 20.04. I haven't tested on RHEL.
Steps to reproduce the issue:
Describe the results you received:
If you're unlucky you're gonna get:
Describe the results you expected:
The container should be created successfully.
Additional information you deem important (e.g. issue happens only occasionally):
The issue only happens occasionally and I couldn't find a way to reproduce it reliably.
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? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
vps on aws
The text was updated successfully, but these errors were encountered: