What is the expected behaviour in redefining the compose.yaml #522
Replies: 1 comment
-
HI, it was my mistake. Sorry for the spam. I didn't know how the redirection of things in docker/podman compose. I need to define the volume as such: - /run/user/1001/podman/podman.sock:/var/run/docker.sock. After that, the redirection works as aspected. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🛡️ Security Policy
📝 Describe your problem
Hello people,
i tried today to make dockge run in a user context. Therefore i activated the podman.sock as a specified podmanuser and modified the compose.yaml.
I changed the volumes from:
- /var/run/docker.sock:/var/run/docker.sock
to- /run/user/1001/podman/podman.sock:/run/user/1001/podman/podman.sock
Therefore i can rollup the dockge-container with podman-compose up.
If I want to compose any other compose.yaml on localhost:5001 (nginx, hedgedoc), I assumed that dockge will use
/run/user/1001/podman/podman.sock
.But it tries to use the
/var/run/docker.sock
.Do you have any idea why this happens?
Greetings
cishard
📝 Error Message(s) or Log
🐻 Dockge Version
1.4.2
💻 Operating System and Arch
RHEL 9.3
🌐 Browser
Mozilla Firefox 115.10.0esr
🐋 Docker Version
podman version 4.9.4-rhel
🟩 NodeJS Version
No response
Beta Was this translation helpful? Give feedback.
All reactions