Podman-compose mount volume incorrectly under Windows with podman machine on WSL #22684
Labels
kind/bug
Categorizes issue or PR as related to a bug.
machine
stale-issue
windows
issue/bug on Windows
Issue Description
When using podman-compose to bring up below container. The volume mapping is incorrectly mapped, it automatically adds "/mnt/d" before each of the volume entry in compose file.
podman-compose v1.1.0
Compose file below:
services:
ibml:
image: /nvidia/cuda
container_name: ibml_engine
build:
context: .\IBML
args:
APP_VERSION: latest
volumes:
- /mnt/e/Data:/mnt/e/Data
- /mnt/d/Logs:/mnt/d/Logs
networks:
candela-net:
ipv4_address: 172.168.0.11
dns:
- "8.8.8.8"
devices:
- nvidia.com/gpu=all
security_opt:
- "label=disable"
If you inspect the container which it brought up. You can see volumes are mount as below
/mnt/d/mnt/e/Data:/mnt/e/Data /mnt/d/mnt/d/Logs:/mnt/d/Logs
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The volume mounted as
/mnt/d/mnt/e/Data:/mnt/e/Data /mnt/d/mnt/d/Logs:/mnt/d/Logs
Describe the results you expected
Then volume should be mounted as
/mnt/e/Data:/mnt/e/Data /mnt/d/Logs:/mnt/d/Logs
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: