-
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
Both RootfsImageName and RootfsImageId must be set if either is set #8558
Comments
Can you try |
Since it was related to names, I tried tagging the build with
It seems that only the tagged and
|
I see the same issue on Ubuntu, version
|
I think we need to get this fixed for 2.2.1 |
I agree, do you know what is causing it? |
@rhatdan No idea, haven't found time to look into this. |
git bisect says it's 410fa53 To be exactly its caused by these lines: podman/pkg/specgen/generate/container_create.go Lines 95 to 106 in f01630a
@vrothberg PTAL |
Looking into it now. |
When creating a container, do not clear the input-image name before looking up image names. Also add a regression test. Fixes: containers#8558 Signed-off-by: Valentin Rothberg <[email protected]>
-> #8623 |
#8623 fixes it for me, thank you! |
As suggested by @edsantiago, add a comment to the regression test of containers#8558 to better document the context. Signed-off-by: Valentin Rothberg <[email protected]>
[CI:DOCS] add comment to #8558 regression test
When creating a container, do not clear the input-image name before looking up image names. Also add a regression test. Fixes: containers#8558 Signed-off-by: Valentin Rothberg <[email protected]> <MH: Fixed cherry-pick conflicts> Signed-off-by: Matthew Heon <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Since I upgraded to 2.2.0, I can no longer run containers from successful intermediate build steps.
Steps to reproduce the issue:
With
--log-level=debug
:Describe the results you expected:
I expected a shell to be launched in a new container.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):(I edited the PKGBUILD to build from git but it seems that master does not have the v2.2.0 tag, hence the weird version.)
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: