Open SamLowryMOI opened 1 year ago
Hit the same issue.
My docker-compose.yml line:
run/podman/podman.sock:/var/run/docker.sock:Z
becomes
-v D:\run\podman\podman.sock:/var/run/docker.sock:Z
$ podman-compose --version podman-compose version: 1.0.7 ['podman', '--version', ''] using podman version: 4.9.2 podman-compose version 1.0.7 podman --version podman version 4.9.2 exit code: 0
I installed the latest dev using: pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz
My OS is Windows 11. Above was using the ancient windows command.exe. The same issue occurs with the Msys2 dev environment (native bash shell).
Quick fix is to edit the C:\Python\Lib\site-packages\podman_compose.py and add the check for windows at line 170 as follows: if os.name != 'nt' or (os.name == 'nt' and ".sock" not in mount_src): mount_src = os.path.abspath(os.path.join(basedir, os.path.expanduser(mount_src)))
Describe the bug I try to use portainer. On
podman-compose up -d
- /run/podman/podman.sock:/var/run/docker.sock
in docker-compose.yml becomes-v E:\run\podman\podman.sock:/var/run/docker.sock:Z
To Reproduce docker-compose.yml on E:\Docker\portainer
Output
Please make sure it's not a bug in podman (in that case report it to podman) If i use
on the command line everything works fine.
please try to reproduce the bug in latest devel branch Sorry, don't know how.
Expected behavior
instead of
Actual behavior
Environment: