Skip to content
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

rootless `podman export ... -o` fails #2381

Closed
vrothberg opened this issue Feb 20, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@vrothberg
Copy link
Member

commented Feb 20, 2019

[valentin@nebuchadnezzar libpod]$ podman export 254 -o foo.tar
Error: error creating file "foo.tar": open foo.tar: permission denied

... while redirecting ... > foo.tar works. I assume that's namespace related but we might need to document that in the manpage (and the help message).

@giuseppe giuseppe added the rootless label Feb 20, 2019

@giuseppe

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

do you get any error if you try buildah unshare touch foo.tar from the same directory?

@vrothberg

This comment has been minimized.

Copy link
Member Author

commented Feb 21, 2019

$ buildah unshare
$ podman export ... -o foo.tar

works.

@vrothberg

This comment has been minimized.

Copy link
Member Author

commented Feb 21, 2019

If I do a buildah unshare touch foo.tar and try to export after, outside the namespace, it doesn't work.

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 21, 2019

rootless: force same cwd when re-execing
when joining an existing namespace, we were not maintaining the
current working directory, causing commands like export -o to fail
when they weren't referring to absolute paths.

Closes: containers#2381

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
@rhatdan

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

ls -l foo.tar

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 21, 2019

rootless: force same cwd when re-execing
when joining an existing namespace, we were not maintaining the
current working directory, causing commands like export -o to fail
when they weren't referring to absolute paths.

Closes: containers#2381

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 22, 2019

rootless: force same cwd when re-execing
when joining an existing namespace, we were not maintaining the
current working directory, causing commands like export -o to fail
when they weren't referring to absolute paths.

Closes: containers#2381

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 22, 2019

rootless: force same cwd when re-execing
when joining an existing namespace, we were not maintaining the
current working directory, causing commands like export -o to fail
when they weren't referring to absolute paths.

Closes: containers#2381

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 22, 2019

rootless: force same cwd when re-execing
when joining an existing namespace, we were not maintaining the
current working directory, causing commands like export -o to fail
when they weren't referring to absolute paths.

Closes: containers#2381

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.