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.

Sign up for GitHub

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

Jump to bottom

rootless podman export ... -o fails #2381

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

rootless podman export ... -o fails #2381

vrothberg opened this issue Feb 20, 2019 · 4 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. rootless

Comments

@vrothberg
Copy link
Member 

[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
Copy link
Member

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

@vrothberg
Copy link
Member Author 

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

works.

@vrothberg
Copy link
Member Author

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
@giuseppe
rootless: force same cwd when re-execing
a1d633c 
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 giuseppe mentioned this issue Feb 21, 2019
Merged
@rhatdan
Copy link
Member

rhatdan commented Feb 21, 2019

ls -l foo.tar

giuseppe added a commit to giuseppe/libpod that referenced this issue Feb 21, 2019
@giuseppe
rootless: force same cwd when re-execing
a4f7735 
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
@giuseppe
rootless: force same cwd when re-execing
3dc52d2 
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
@giuseppe
rootless: force same cwd when re-execing
5051813 
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
@giuseppe
rootless: force same cwd when re-execing
8984ba7 
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>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. rootless
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@giuseppe @rhatdan @vrothberg