You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The subpath option for volumes with docker-compose get's silently ignored.
There have been comments about this in #20661. But this Issue has been closed since podman 5.4.0 added support for volume subpaths using podman run/create ---mount ...subPath=.
There has also been support for subpaths with podman kube play#16803 which works fine.
test-full and test-subpath services will echo "full"
Describe the results you expected
test-full should echo "full" and test-subpath should echo "sub".
podman run --rm -it --mount type=volume,source=podman-compose-subvolume_data,target=/mnt,subpath=sub alpine cat /mnt/testfile does in fact return "sub"
Issue Description
The subpath option for volumes with docker-compose get's silently ignored.
There have been comments about this in #20661. But this Issue has been closed since podman 5.4.0 added support for volume subpaths using
podman run/create ---mount ...subPath=
.There has also been support for subpaths with
podman kube play
#16803 which works fine.Steps to reproduce the issue
Steps to reproduce the issue
podman compose up
Describe the results you received
test-full and test-subpath services will echo "full"
Describe the results you expected
test-full should echo "full" and test-subpath should echo "sub".
podman run --rm -it --mount type=volume,source=podman-compose-subvolume_data,target=/mnt,subpath=sub alpine cat /mnt/testfile
does in fact return "sub"podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: