-
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
Failed to save an image as a 'docker-dir' format on remote environment #15897
Comments
@vrothberg is this even something we should support on remote? |
We do support it. Looks like an unfortunate regression. I get an EPERM when trying that. Screams to have a look at the tests. |
@boaz0, interested in tackling this issue? |
sure, assign it to me. 😄 |
Thanks! |
A friendly reminder that this issue had no activity for 30 days. |
@boaz0 any update on this? |
Yeah, but I am not done with this. It seems like we didn't have support for that on the API. |
A friendly reminder that this issue had no activity for 30 days. |
Make sure that the directory formats are not just substituted with their archive counterparts but actually tar'ed up directories. Also make sure that the clients don't get chown errors by setting rootless user and group ID instead of O when running in the user namespace. Fixes: containers#15897 Signed-off-by: Valentin Rothberg <[email protected]>
I opened #18563 to fix the issue. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman-remote save --format docker-dir
saves an image as adocker-archive
format.Describe the results you received:
An image is saved as
docker-archive
format.Describe the results you expected:
An image is saved as
docker-dir
format.Additional information you deem important (e.g. issue happens only occasionally):
Succeeded to save a image as a
docker-dir
format on local environment.podman-remote version
podman-remote info
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
KVM, fedora36
The text was updated successfully, but these errors were encountered: