Bug 1772460
Summary: | After upgrading my silverblue to crun-0.10.5, toolbox stopped to work. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin Vala <vala.martin> |
Component: | crun | Assignee: | Giuseppe Scrivano <gscrivan> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | bryanhoop, gscrivan, lsm5, mpitt, splinux25 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | crun-0.10.6-1.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-19 01:36:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Vala
2019-11-14 12:16:51 UTC
fixed with: https://github.com/containers/crun/pull/178 Please test toolbox before pushing container package updates to Bodhi :) Of course what we really need is dependent CI and gating. (In reply to Jens Petersen from comment #2) > Please test toolbox before pushing container package updates to Bodhi :) testing toolbox wouldn't have been enough. The issue happens when the source is a symlink as it is the case on Silverblue. *** Bug 1773440 has been marked as a duplicate of this bug. *** FEDORA-2019-4b4957bbc6 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4b4957bbc6 crun-0.10.6-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. I'm running into this issue on crun-0.10.6: [conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied DEBU[0000] Received: -1 DEBU[0000] Cleaning up container a3f4802cea8f85f6d7a99c4f7533f927e26c8a9d69fdf6028f8e3c179db7706b DEBU[0000] Network is already cleaned up, skipping... DEBU[0000] unmounted container "a3f4802cea8f85f6d7a99c4f7533f927e26c8a9d69fdf6028f8e3c179db7706b" DEBU[0000] Cleaning up container a3f4802cea8f85f6d7a99c4f7533f927e26c8a9d69fdf6028f8e3c179db7706b DEBU[0000] Network is already cleaned up, skipping... DEBU[0000] Container a3f4802cea8f85f6d7a99c4f7533f927e26c8a9d69fdf6028f8e3c179db7706b storage is already unmounted, skipping... DEBU[0000] Container a3f4802cea8f85f6d7a99c4f7533f927e26c8a9d69fdf6028f8e3c179db7706b storage is already unmounted, skipping... DEBU[0000] ExitCode msg: "creating file '/home/bryan/.local/share/containers/storage/overlay/1c23f4e29c00e151b4f10d11580c352a05539b4acda4d9b513101d5d595d19d7/merged/run/secrets': permission denied: oci runtime permission denied error" ERRO[0000] creating file '/home/bryan/.local/share/containers/storage/overlay/1c23f4e29c00e151b4f10d11580c352a05539b4acda4d9b513101d5d595d19d7/merged/run/secrets': Permission denied: OCI runtime permission denied error If I terminate a container then I cannot create a new container of the same name: ERRO[0000] error creating container storage: the container name "mc_guacgui" is already in use by "07ddddde745f0848dd22264828d4aa7503ca10721678ca8c1326f2251561bc87". You have to remove that container to be able to reuse that name.: that name is already in use That container is not listed in `podman container ls -a`, so I must remove it with: podman rm --force --storage 07ddddde745f0848dd22264828d4aa7503ca10721678ca8c1326f2251561bc87 After this, if I try to rerun podman run to build the container, I get the OCI error listed above. If I reboot then I can run podman run successfully until I terminate the container, which brings me back into the loop. So I am stuck only running the same container ONCE per reboot. |