Define user when using docker compose about uptime-kuma HOT 5 CLOSED

See https://github.com/louislam/uptime-kuma/wiki/Environment-Variables#docker-specific-environment-variables
You could use the standard PUID/PGID. I have not tested if they work.

v2 will come with full support of running as another user via the -rootless tags. See #4052 for further context.
See #4171 for what bugfixes still need to happen until a first beta can be issued.

from uptime-kuma.

Hmm, that's strange... The document says that the default PUID and GUID are 1000, but when I set these values:

    environment:
      - PUID=1000
      - PGID=1000

in a docker compose, the Uptime Kuma cannot check the container status. Any idea why?

from uptime-kuma.

cannot check the container status

How have you mounted the docker socket?
What are the permissions of said socket?
Can the chosen PUID/PGID access said socket?

from uptime-kuma.

You can find my docker compose below. I have added it as read only, due to the checking doesn't require a write permission.

srw-rw---- 1 root docker 0 Jan 14 12:14 /var/run/docker.sock

The user with PIUD 1000 is part of the docker group, so it has an access to it.

version: '3.8'

services:
  uptime-kuma:
    image: louislam/uptime-kuma:alpine
    container_name: uptime-kuma
    environment:
      - PUID=1000
      - PGID=1000
    volumes:
      - /mnt/Docker/uptime-kuma:/app/data
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 3001:3001
    restart: always
    network_mode: bridge
    cpus: 0.5
    mem_limit: 400M

from uptime-kuma.

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

from uptime-kuma.