Originally created by @atakiya on GitHub (May 25, 2025).
Problem
Currently komodo periphery can only be used as a container on podman setups by rebinding the host's /run/podman/podman.sock to /var/run/docker.sock
This isn't possible with the systemd variant of komodo periphery as there is no config variable to change the listen socket.
Why?
Better podman support would be nice for anyone not using docker
Originally created by @atakiya on GitHub (May 25, 2025).
## Problem
Currently komodo periphery can only be used as a container on podman setups by rebinding the host's `/run/podman/podman.sock` to `/var/run/docker.sock`
This isn't possible with the systemd variant of komodo periphery as there is no config variable to change the listen socket.
## Why?
Better podman support would be nice for anyone not using docker
This is also a problem on rootless docker (using user systemd periphery). I didn't rebind, I simply symlinked /var/run/docker.sock to /var/run/user/1000/docker.sock. It's not my favorite solution but works for now..
@MrOwen commented on GitHub (Aug 10, 2025):
This is also a problem on rootless docker (using user systemd periphery). I didn't rebind, I simply symlinked `/var/run/docker.sock` to `/var/run/user/1000/docker.sock`. It's not my favorite solution but works for now..
Did you try Environment="DOCKER_HOST=/run/podman/podman.sock" in the periphery.service systemd file?
@mbecker20 commented on GitHub (Aug 11, 2025):
Did you try `Environment="DOCKER_HOST=/run/podman/podman.sock"` in the `periphery.service` systemd file?
Did you try Environment="DOCKER_HOST=/run/podman/podman.sock" in the periphery.service systemd file?
Yeah that works. Thank you!
For anyone stumbling over this and wondering how to get periphery to cooperate step-by-step:
make sure the podman socket is enabled (systemctl enable --now podman.socket)
as mentioned in the above comment, make sure the service file has the DOCKER_HOST env variable set to the podman socket (either edit service file, or add drop-in)
make sure to have docker cli shims installed (e.g. dnf install podman-docker on fedora)
restart periphery service
@atakiya commented on GitHub (Aug 15, 2025):
> Did you try `Environment="DOCKER_HOST=/run/podman/podman.sock"` in the `periphery.service` systemd file?
Yeah that works. Thank you!
---
For anyone stumbling over this and wondering how to get periphery to cooperate step-by-step:
- make sure the podman socket is enabled (`systemctl enable --now podman.socket`)
- as mentioned in the above comment, make sure the service file has the `DOCKER_HOST` env variable set to the podman socket (either edit service file, or add drop-in)
- make sure to have docker cli shims installed (e.g. `dnf install podman-docker` on fedora)
- restart periphery service
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @atakiya on GitHub (May 25, 2025).
Problem
Currently komodo periphery can only be used as a container on podman setups by rebinding the host's
/run/podman/podman.sockto/var/run/docker.sockThis isn't possible with the systemd variant of komodo periphery as there is no config variable to change the listen socket.
Why?
Better podman support would be nice for anyone not using docker
@MrOwen commented on GitHub (Aug 10, 2025):
This is also a problem on rootless docker (using user systemd periphery). I didn't rebind, I simply symlinked
/var/run/docker.sockto/var/run/user/1000/docker.sock. It's not my favorite solution but works for now..@mbecker20 commented on GitHub (Aug 11, 2025):
Did you try
Environment="DOCKER_HOST=/run/podman/podman.sock"in theperiphery.servicesystemd file?@atakiya commented on GitHub (Aug 15, 2025):
Yeah that works. Thank you!
For anyone stumbling over this and wondering how to get periphery to cooperate step-by-step:
systemctl enable --now podman.socket)DOCKER_HOSTenv variable set to the podman socket (either edit service file, or add drop-in)dnf install podman-dockeron fedora)