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 documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
Hi!
I have encountered the following error message in the logs right at startup:
Fri, 18 Oct 2024 08:56:02 UTC ERR Cannot create Docker client error="permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \"http://%2Fvar%2Frun%2Fdocker.sock/v1.44/version\": dial unix /var/run/docker.sock: connect: permission denied" provider=docker
At first I thought there must be a bug, because I correctly set everything up according to the docs. But then I compared the settings with the ones I had in place for my traefik container - which is also relying on the docker.sock/podman.sock. I had similar issues there until I added the security flag:
--security-opt label=type:container_runtime_t
Which enables the container in actually read the docker sock while not being a completely privileged container. So I would propose to update the documentation on the doc website to add/mention this.
Expected behaviour
Proposed documentation:
version: "3.5"services:
diun_app:
image: docker.io/crazymax/diun:latest# security_opt is neccessary if you use podman in rootless mode to apply the correct SELinux rulessecurity_opt:
- "label=type:container_runtime_t"volumes:
- "./data:/data:z"# root mode
- "/run/podman/podman.sock:/var/run/docker.sock:ro"# rootless mode#- "$XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock:ro"# or#- "/run/user/1000/podman/podman.sock:/var/run/docker.sock:ro"environment:
- "TZ=Europe/Paris"
- "DIUN_WATCH_WORKERS=20"
- "DIUN_WATCH_SCHEDULE=0 */6 * * *"
- "DIUN_WATCH_JITTER=30s"
- "DIUN_PROVIDERS_DOCKER=true"labels:
- "diun.enable=true"restart: always
$ podman version
Client: Podman Engine
Version: 4.9.4-rhel
API Version: 4.9.4-rhel
Go Version: go1.21.13 (Red Hat 1.21.13-4.el9_4)
Built: Mon Oct 14 03:26:59 2024
OS/Arch: linux/arm64
Docker Compose config
No response
Logs
Fri, 18 Oct 2024 08:56:02 UTC INF Starting Diun version=v4.28.0
Fri, 18 Oct 2024 08:56:02 UTC INF Configuration loaded from 8 environment variable(s)
Fri, 18 Oct 2024 08:56:02 UTC INF Cron triggered
Fri, 18 Oct 2024 08:56:02 UTC ERR Cannot create Docker client error="permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \"http://%2Fvar%2Frun%2Fdocker.sock/v1.44/version\": dial unix /var/run/docker.sock: connect: permission denied" provider=docker
Fri, 18 Oct 2024 08:56:02 UTC WRN No image found
Fri, 18 Oct 2024 08:56:02 UTC INF Jobs completed added=0 failed=0 skipped=0 unchanged=0 updated=0
Fri, 18 Oct 2024 08:56:02 UTC INF Cron initialized with schedule 0 */6 * * *
Fri, 18 Oct 2024 08:56:02 UTC INF Next run in 3 hours 4 minutes (2024-10-18 12:00:07.199599131 +0000 UTC)
Additional info
No response
The text was updated successfully, but these errors were encountered:
Support guidelines
I've found a bug and checked that ...
Description
Hi!
I have encountered the following error message in the logs right at startup:
I followed the documentation for running DIUN under docker and also had a look on the section of podman:
https://crazymax.dev/diun/install/docker/
I use diun in a rootless podman setup.
At first I thought there must be a bug, because I correctly set everything up according to the docs. But then I compared the settings with the ones I had in place for my traefik container - which is also relying on the docker.sock/podman.sock. I had similar issues there until I added the security flag:
Which enables the container in actually read the docker sock while not being a completely privileged container. So I would propose to update the documentation on the doc website to add/mention this.
Expected behaviour
Proposed documentation:
Actual behaviour
Current documentation:
Steps to reproduce
Diun version
v4.28.0
Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: