-
Notifications
You must be signed in to change notification settings - Fork 221
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
Failed to initialize container #687
Comments
At least, a workaround is rolling back the upgrade. |
same issue, @ptomato, except my rollback didn't provide a workaround. not sure where to go from here, short of giving up on Silverblue and going back to Workstation... |
These lines confirm that the entry point of the container got started (as PID 12307):
Hence, this is different from #669 where the entry point didn't even start because the basic runtime environment is busted. What's happening here is that the What does this say:
|
I am getting a similar issue, and
|
What's the output from |
Can you try running with the latest version of |
How urgently do you need this info? I am happy to provide it but it may take me quite some time until I find a moment when I can intentionally upgrade my system to a broken state and then downgrade it again, since I need to use it for work in the meantime 😄 |
It's ok; no stress. All of us have plenty on our plates to keep us occupied. :) |
I have the same issue since the last silverblue update which updated conman.
Selecting previous ostree in Grub with working toolbox:
|
Wanted to point out the post I made here a little bit back, also attempting to follow what is in this thread:
root is on btrfs, as that may have something to do with this. Attempting to follow the golden path silverblue installation. (looked at what the automatic partitioning did and copied it with custom but with slightly different sizes).
|
Looks like both @djselbeck and @storrgie are having problems with At least in @djselbeck 's case, |
Could we have at least task somewhere to make unit tests for it? |
So far, it looks like a |
Even if the reason is in |
Obviously there are basic automated tests. I am not sure why those aren't failing, though. At least Sometimes, writing good tests isn't quite so easy. :) |
Thanks, I didn't know that! That's really important.
Yeah, probably we should make it so :) |
toolbox keeps stopping working. I had the issue where my uid and gid were not the same, so I change it so they're the same, and get access back to toolbox, but now, I'm hit with this issue and even downgrading conmon as suggested above don't fix the issue. I get the same behaviour as @storrgie. |
@storrgie mentioned btrfs may have something to do with it. |
I do use btrfs over luks, and my layout is as follow:
|
@debarshiray sorry it took me a moment:
Starting fresh (I think) by killing off the
😢
Next test? |
Ok, so clearly @djselbeck and @storrgie are facing different bugs. Not sure about @ptomato yet. @storrgie could you please file a separate issue about Btrfs and |
Additionnal informations, as I said, I run a fully uptodate Silverblue 33:
Here's when I try to attach with full debug:
The regular toolbox enter goes like this:
My id output is:
|
I too cannot use my containers
only the fedora 33 container showed different error:
and then it changed to the same error the other containers show:
|
This works for me. Edit
reboot and try |
The issue for me is fixed with a recent update in F33 silverblue. Fixed podman info:
|
I am having this issue on f34, as a workaround I followed @biji advice. Happy to porovide more info to trooubleshoot. |
As in @djselbeck's case, the issue is resolved for me on the latest Fedora 33 Silverblue. |
I'm also having this issue on Fedora Silverblue 34.
I may have been the cause, though, because I created a group called
Using
|
@ptomato and @djselbeck are reporting that their problems got fixed. Thanks for confirming that! Closing. |
Has this bug returned? I'm hitting it on a F38 container on Silverblue F38 host |
lol, breaks again? |
Describe the bug
Toolbox fails to start after an upgrade and a reboot. This seems to be a different error than #669, and I did not do any unusual updates as described there, so I'm creating a different issue.
Steps how to reproduce the behaviour
toolbox enter
Expected behaviour
Toolbox environment should start as normal.
Actual behaviour
Screenshots
N/A
Output of
toolbox --version
(v0.0.90+)toolbox version 0.0.99
Toolbox package info (
rpm -q toolbox
)toolbox-0.0.99-1.fc33.x86_64
Output of
podman version
Podman package info (
rpm -q podman
)podman-2.2.1-1.fc33.x86_64
Info about your OS
Fedora Silverblue 33, freshly updated as of the time of writing
Additional context
This happened after a updating the Silverblue image to the latest, and rebooting. The toolbox image is Fedora 33.
Here's a list of packages upgraded (note, it's the list I got from
rpm-ostree rollback
, so you have to read it in reverse):The text was updated successfully, but these errors were encountered: