Skip to content

fix podman-remote save -f oci-dir/docker-dir#28903

Open
Luap99 wants to merge 2 commits into
podman-container-tools:mainfrom
Luap99:fix-chrootarchive-remote
Open

fix podman-remote save -f oci-dir/docker-dir#28903
Luap99 wants to merge 2 commits into
podman-container-tools:mainfrom
Luap99:fix-chrootarchive-remote

Conversation

@Luap99

@Luap99 Luap99 commented Jun 10, 2026

Copy link
Copy Markdown
Member

With podman-remote we do not enter a our user namespace like we do with local podman so we keep running with the real user id.

So if we then try to use chrootarchive as normal user it fails with: creating mount namespace before pivot: operation not permitted

So simply revert back to the normal archive code.

Now the more interesting thing is we do have a test "podman save to directory with oci format" but it never runs rootless+remote in our CI system with our current matrix as we wanted to reduce jobs.
So rethink the matrix and add one such job as this shows it is needed.

Fixes: 25aee24 ("use chrootarchive over plain archive package")

Does this PR introduce a user-facing change?

Fixed an issue that made podman-remote save -f oci-dir/docker-dir fail on linux. 

With podman-remote we do not enter a our user namespace like we do with
local podman so we keep running with the real user id.

So if we then try to use chrootarchive as normal user it fails with:
creating mount namespace before pivot: operation not permitted

So simply revert back to the normal archive code.

Now the more interesting thing is we do have a test
"podman save to directory with oci format" but it never runs
rootless+remote in our CI system with our current matrix as we wanted to
reduce jobs.
So rethink the matrix and add one such job as this shows it is needed.

Fixes: 25aee24 ("use chrootarchive over plain archive package")

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
@github-actions github-actions Bot added the CI label Jun 10, 2026
@Luap99 Luap99 added the No New Tests Allow PR to proceed without adding regression tests label Jun 10, 2026
@packit-as-a-service

Copy link
Copy Markdown

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

@mheon

mheon commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

LGTM

So when running remote and rootless tests the buildImage() thing has one
big problem because it used the main test tmpdir as context.

However that dir also holds all the image layers with files that are
owned by other uids and because podman-remote does not use the userns it
cannot read some files and then fails when trying to tar up the context
dir.

To fix this use an extra sub directory.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI No New Tests Allow PR to proceed without adding regression tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants