-
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
Podman Volume Import does not work after performing Podman Volume Export #14411
Comments
|
Nevermind. Podman volume import does not create a new volume. It can only be used to restore into an existing volume. |
When the volume does not exist we should output an error stating so and not some generic one. Fixes containers#14411 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
When the volume does not exist we should output an error stating so and not some generic one. Fixes containers#14411 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Thank you @Luap99 for quickly identifying the issue. I came here to ask if I could help with documentation updates, but you have already taken care of that via your commits! Great stuff. Will this also end up reflected in docs.podman.io and in the Red Hat docs? Not sure if the Red Hat docs are at all relevant in this context. |
docs.podman.io will be updated automatically, are you referring to any special Red Hat docs? The shipped man pages are updated with the podman version. |
When the volume does not exist we should output an error stating so and not some generic one. Fixes containers#14411 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
Image pulls and runs successfully
Describe the results you received:
podman volume import
fails as follows[bblasco@bblasco-t490s tmp]$ podman volume import somedata jenkins-data.tar
Error: no volume data found
Describe the results you expected:
Volume should have imported successfully and a new volume visible in
podman volume ls
Additional information you deem important (e.g. issue happens only occasionally):
Always happens on both podman 3.4.7 and 4.1.0
Output of
podman version
:On Fedora 36
On Fedora 35:
Output of
podman info --debug
:On Fedora 36
Package info (e.g. output of
rpm -q podman
orapt list podman
):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.):
Baremetal deployment on Fedora 36 on an Intel NUC.
The text was updated successfully, but these errors were encountered: