-
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
Coredump: "panic: runtime error: slice bounds out of range [:-1]" with Quadlet/YAML starting #21080
Comments
@rugk Thanks for reporting this issue. I believe I have found the cause of the crash and opened a PR for it. However, since I don't have the YAML file you are using I cannot know for certain. Can you please check if the YAML file includes an annotation with the key The way this annotation works is that its value is supposed to have the source volume and the options separated by So, if I am correct in my finding, you should fix your YAML file by either adding the options if needed, or otherwise removing the annotation. |
This is the beginning of the YAML:
This is the only place |
@rugk thanks for the info. From the YAML file, I see that the fix is correct in terms of not crashing. This issue still raises a question about |
I guess this is the same bug:
|
@rugk the fix for this issue was not part of v4.8.x or v4.9.x and therefore will only be released in v5.x |
Issue Description
I basically did a
systemctl --user start nextcloud.service
to start a Quadlet.kube
file with a YAML quite complex and generated out of running containers (withpodman generate kube
before).Then suddenly podman coredumped, and I guess it should not. 🙈
Steps to reproduce the issue
The Quadlet I use:
The generated system service (via
systemctl --user daemon-reload
):systemctl --user start nextcloud.service
as said then causes this.podman ps
shows nothing was running.Describe the results you received
Log:
Describe the results you expected
no coredump, at least some error
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Fedora CoreOS 39
Additional information
The last issue of that kind seems to be from 2021.
I can provide the YAML file if asked for, but I would need to check and remove sensitive information from it and it's quite long.
I have saved the 7,5 MB
core.podman.1002.4d8fb586128f4733857351106e14a7d6.1053332.1703260582000000.zst
and may also provide that privately to someone upon request.The text was updated successfully, but these errors were encountered: