I have an application that populates volume content by creating a tar stream and sending it to a container with a mounted volume.
With docker I can mount a volume to /mymount and have the tar contain /mymount/folder/file and use the path / with the PUT request and the volume is populated as expected. With podman the volume remains empty (although the request does return 200), unless I alter the tar to contain folder/file and use the path /mymount with the PUT request.
Steps to reproduce the issue
Steps to reproduce the issue
Create tarfile with absolute paths that include the volume mount point
Send the tarfile as a PUT request to the /containers/{id}/archive endpoint for a container with a new volume mounted at the volume mount point
Verify the volume content
Describe the results you received
The volume remains empty
Describe the results you expected
The volume should contain the files from the tar (eg /mymount/myfile or /mymount/mydir/myfile)
Issue Description
I have an application that populates volume content by creating a tar stream and sending it to a container with a mounted volume.
With docker I can mount a volume to
/mymount
and have the tar contain/mymount/folder/file
and use the path/
with the PUT request and the volume is populated as expected. With podman the volume remains empty (although the request does return 200), unless I alter the tar to containfolder/file
and use the path/mymount
with the PUT request.Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The volume remains empty
Describe the results you expected
The volume should contain the files from the tar (eg /mymount/myfile or /mymount/mydir/myfile)
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Tested with podman 4.7.0 and 4.9.3 under Fedora 39. Same behavior on both.