"Error: failed to start container fedora-toolbox-32" on Fedora Silverblue #500
Comments
rugk
changed the title
|
Repulling comntainer… …did not work either. |
|
Hey @rugk! It seems you're still running the Shell Toolbox (v0.0.18) even though your current deployment of Silverblue should already contain v0.0.92. Can you, please, try to upgrade your machine again and try to use the new Toolbox?? |
|
|
|
Hmm, odd. I have the same deployment and a newly created container is running alright. According to the output of |
|
Without knowing anything about the system, maybe the logs are still from an old toolbox version and it did not write any new logs?
IIRC I created that container a few months ago, not that long ago. |
Good point! That actually may be the reason. So, this happens with an old container... Can the issue be reproduced with a new container?? |
|
I have the same issue with Fedora 31 Workstation
Packages Altered:
Upgrade librados2-2:14.2.10-1.fc31.x86_64 @updates
Upgraded librados2-2:14.2.9-2.fc31.x86_64 @@System
Upgrade librbd1-2:14.2.10-1.fc31.x86_64 @updates
Upgraded librbd1-2:14.2.9-2.fc31.x86_64 @@SystemIn case there was no reboot yesterday, the previous update did: I could supply the output of podman inspect, but since I have 8 separate containers failing the same way, all at the same time, I doubt it is a container specific problem. Unless a EDIT: So far, a newly created container is working correctly |
|
After building up a new container with the same (very close) configuration/content as one of the failing cases, I did podman inspect on each of them, and compared the outputs. The interesting differences are: old failing new working
[ [
{ {
"State": { "State": {
"OciVersion": "1.0.1-dev", | "OciVersion": "1.0.2-dev",
}, },
"MountLabel": "system_u:object_r:container_file_t:s0:c26,c243", | "MountLabel": "system_u:object_r:container_file_t:s0:c361,c604",
"Config": { "Config": {
"Env": [ "Env": [
"container=oci", | "container=podman",
], ],
}, },
"HostConfig": { "HostConfig": {
"IpcMode": "host", | "IpcMode": "private",
"MemorySwappiness": -1, | "MemorySwappiness": 0,
"Ulimits": [ | "Ulimits": [],
{ <
"Name": "RLIMIT_NOFILE", <
"Soft": 524288, <
"Hard": 524288 <
}, <
{ <
"Name": "RLIMIT_NPROC", <
"Soft": 63377, <
"Hard": 63377 <
} <
], <
} }
} }
] ] |
Obviously yes, because your command is wrong… 🙃 😉 |
|
:) % toolbox --version
toolbox: unrecognized option '--version'
Try 'toolbox --help' for more information.Doesn't work either |
|
Thank you @mMerlin for all the information! It is very helpful! With this I know, this is caused by Podman itself. I found some issues in Podman's bug tracker: containers/podman#6857, containers/podman#6389. Based on the changelog entry for Podman v2.0.2, the issue should be already fixed. Can you confirm that the issue is resolved or is it still present?
On Fedora 31 is still Toolbox v0.0.18 which does not have the option |
|
Apparently not fixed with versions I have available. Starting from: % podman --version
podman version 2.0.1
% rpm -q toolbox
toolbox-0.0.18-2.fc31.noarch
% sudo dnf upgrade podman --enablerepo=updates-testing --best
% dnf history info 196
…
Command Line : upgrade podman --enablerepo=updates-testing --best
Comment :
Packages Altered:
Upgrade podman-2:2.0.2-1.fc31.x86_64 @updates-testing
Upgraded podman-2:2.0.1-1.fc31.x86_64 @@System
Upgrade podman-docker-2:2.0.2-1.fc31.noarch @updates-testing
Upgraded podman-docker-2:2.0.1-1.fc31.noarch @@System
Upgrade podman-plugins-2:2.0.2-1.fc31.x86_64 @updates-testing
Upgraded podman-plugins-2:2.0.1-1.fc31.x86_64 @@System
% podman --version
podman version 2.0.2With a system reboot for good measure, the old containers are still failing to start. No change in the symptoms. |
|
Looks like on F31 the update did not fix the issue according to Bodhi: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c510ceb7db. I encourage you to comment on the update and give it a negative karma. @rugk, I believe the same could be done for the F32 update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-19924b556e. Apart from this, I'd possibly comment on one of the mentioned issue tickets to make it known that the bug has not been fixed. |
|
I added a reproducer to the upstream issue. |
|
So it seems like we should sort it out in Podman, right? Duplicate of containers/podman#6389 and containers/podman#6857 |
|
Sorry how to fix this? Tried Thanks |
Fedora Silverblue 32, 32.20200712.0 (2020-07-12T00:42:58Z)
$USER= rugklogs
podman container listlists no container.The text was updated successfully, but these errors were encountered: