-
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
Silverblue toolbox script broke because rootless 'podman create' insists on having a command specified #1452
Comments
@giuseppe PTAL |
I think I know what's going on here - |
When used as PID 1, /bin/sh takes 3248 kB compared to the 4136 kB taken by /bin/bash. It's not a lot, but is memory that can be saved for free. As a nice side-effect, this unbreaks 'create' with podman-0.9.1 because 'podman create ...' doesn't work without a command. containers/podman#1452
yes, we should avoid the command/entrypoint before podman is re-executed. I think this patch could fix it:
@debarshiray do you have any chance to test it out? I'll prepare a proper PR and test it better if can confirm it solves the issue for you |
@giuseppe Could you open a PR? |
Running into this as well via rootless |
do not error out when the storage is not initialized and the entrypoint command is not available for the specified image. Check it when we re-exec in an user namespace and can access the storage. Closes: containers#1452 Signed-off-by: Giuseppe Scrivano <[email protected]>
PR opened here: #1472 |
Yes, #1472 works for me! Thanks. |
/kind bug
Description
Here is the toolbox script that we have been working on for Fedora Silverblue.
If you follow the
README.md
until thefedora-toolbox create
step, then you'll see that thepodman create ...
command fails:This started happening somewhere between
podman-0.8.5
andpodman-0.9.1
.Changing the script like this solves the problem:
Is this a podman regression? Or is this a bug in the toolbox script that was somehow getting papered over in previous podman versions, and should be fixed in the script?
Output of
podman version
:Output of
podman info
:Additional environment details (AWS, VirtualBox, physical, etc.):
This is a physical laptop running Fedora 28 Silverblue 28.20180908.0
The text was updated successfully, but these errors were encountered: