H
Homarr•6mo ago
Murd

Docker integration works, but....it shouldn't?

Heyas, I've got a homarr container running in my homelab and it's all working wonderfully. I've got users created for each container, bind mounts set with appropriate user and group perms, everything working well. What's confusing me though is that the docker integration is working (via adding /var/run/docker.sock as a mounted volume), when I don't think it should be - I haven't added the homarr user into the docker group... Below a snippet of my compose. If there are indentation errors please ignore, it's a copy paste artefact. This is working, 
  
  homarr:
    image: ghcr.io/ajnart/homarr:latest
    container_name: homarr
    hostname: homarr
    extra_hosts: *host-server
    restart: unless-stopped
    networks:
      - core_services_net
      - media_net
    ports:
      - 7575:7575
    environment:
      PUID: 1019
      PGID: 1019
      TZ: Australia/Melbourne
      DISABLE_ANALYTICS: TRUE
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /dockers/homarr/configs:/app/data/configs
      - /dockers/homarr/icons:/app/public/icons
      - /dockers/homarr/data:/data
  
  homarr:
    image: ghcr.io/ajnart/homarr:latest
    container_name: homarr
    hostname: homarr
    extra_hosts: *host-server
    restart: unless-stopped
    networks:
      - core_services_net
      - media_net
    ports:
      - 7575:7575
    environment:
      PUID: 1019
      PGID: 1019
      TZ: Australia/Melbourne
      DISABLE_ANALYTICS: TRUE
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /dockers/homarr/configs:/app/data/configs
      - /dockers/homarr/icons:/app/public/icons
      - /dockers/homarr/data:/data
and here's the perms on the host system: 
# directory showing container is writing files as homarr (1019) user
~$ ls -la /dockers/homarr/
<snip>
drwxrwx---  2 homarr homarr 4096 Jul  5  2024 configs
drwxrwx---  2 homarr homarr 4096 Jun 11 09:31 data
drwxrwx---  2 homarr homarr 4096 Jul  5  2024 icons


# no homarr user in the docker group
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz
homarr:x:1019:cliaz

# the permissions of docker.sock, showing that the Others octal is 0
~$ namei -m /var/run/docker.sock
f: /var/run/docker.sock
 drwxr-xr-x /
 drwxr-xr-x var
 lrwxrwxrwx run -> /run
   drwxr-xr-x /
   drwxr-xr-x run
 srw-rw---- docker.sock
~$ stat -c "%a %n" /var/run/docker.sock
660 /var/run/docker.sock
# directory showing container is writing files as homarr (1019) user
~$ ls -la /dockers/homarr/
<snip>
drwxrwx---  2 homarr homarr 4096 Jul  5  2024 configs
drwxrwx---  2 homarr homarr 4096 Jun 11 09:31 data
drwxrwx---  2 homarr homarr 4096 Jul  5  2024 icons


# no homarr user in the docker group
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz
homarr:x:1019:cliaz

# the permissions of docker.sock, showing that the Others octal is 0
~$ namei -m /var/run/docker.sock
f: /var/run/docker.sock
 drwxr-xr-x /
 drwxr-xr-x var
 lrwxrwxrwx run -> /run
   drwxr-xr-x /
   drwxr-xr-x run
 srw-rw---- docker.sock
~$ stat -c "%a %n" /var/run/docker.sock
660 /var/run/docker.sock
Is there something I'm missing here? Host is Ubuntu 24.04 LTS, Homarr version 0.15.10
7 Replies
Cakey Bot
Cakey Bot•6mo ago
Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Manicraft1001
Manicraft1001•6mo ago
You're running 0.15.10 which is deprecated and we no longer provide support for. See https://homarr.dev/blog/2025/01/19/migration-guide-1.0
Migrate from 0.15.10+ to 1.0.0 | Homarr documentation
In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
Murd
MurdOP•6mo ago
oh, righto. That's given me something else to look into - why watchtower didn't update homarr.... Let me upgrade and confirm I'm still seeing this issue
Manicraft1001
Manicraft1001•6mo ago
Because we use a new image tag. Hence it doesn't auto update
Murd
MurdOP•6mo ago
Ahh yea that'd do it. Righto, Give me a bit and I'll report back. Thanks for the prompt response Ok, v1.0.0 deployed. Gotta say it looks nice! When running without user (PUID / PGID) directive set aka as root, docker containers visible in Tools --> Docker When running with user set as my specific homarr-only user (1019:1019) while not in the dockers group, it errors - as expected. I then added my 1019 user to the dockers group, but still the error: 
 ⨯ [Error [TRPCError]: connect EACCES /var/run/docker.sock] {
  code: 'INTERNAL_SERVER_ERROR',
  digest: '823092188',
  [cause]: [Error: connect EACCES /var/run/docker.sock] {
    errno: -13,
    code: 'EACCES',
    syscall: 'connect',
    address: '/var/run/docker.sock'
  }
}
 ⨯ [Error [TRPCError]: connect EACCES /var/run/docker.sock] {
  code: 'INTERNAL_SERVER_ERROR',
  digest: '823092188',
  [cause]: [Error: connect EACCES /var/run/docker.sock] {
    errno: -13,
    code: 'EACCES',
    syscall: 'connect',
    address: '/var/run/docker.sock'
  }
}
verifying user is in the right group 
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz,homarr
homarr:x:1019:cliaz
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz,homarr
homarr:x:1019:cliaz
I didn't really make this a question - is this the expected outcome? From my understanding of the documentation / linux permissions, it shouldn't be. I would have expected that adding the user (uid:1019) that the container is running as to a group that has RW access to /var/run/docker.sock would be sufficient, but that doesn't seem to be the case. That, or I've stuffed something up somewhere (more likely)
Manicraft1001
Manicraft1001•6mo ago
Murd
MurdOP•6mo ago
Ahh… I had seen that, and I’d interpreted it as “ensure the user (that the container is running as) is in the correct group to access docker files”, hence me adding id: 1019 to the group docker On re-read I think the docs are saying that instead I should be setting PGID to 984, which is the docker group on my system. Won’t lie, don’t fully understand the difference - I figured the inherited access of user 1019 being in group 984 would work*, but clearly not. I’ll test and report back. * eg this is /etc/groups atm, with things not working: 
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz,homarr
homarr:x:1019:cliaz
~$ grep 'homarr\|docker' /etc/group
docker:x:984:cliaz,homarr
homarr:x:1019:cliaz
Yup that's solved it: 
  homarr:
    image: ghcr.io/homarr-labs/homarr:latest
    <snip>
    environment:
      PUID: 1019
      PGID: 984
  homarr:
    image: ghcr.io/homarr-labs/homarr:latest
    <snip>
    environment:
      PUID: 1019
      PGID: 984
Starting with UID='1019', GID='984'
Changing owner to 1019:984, this will take about 10 seconds...
Starting with UID='1019', GID='984'
Changing owner to 1019:984, this will take about 10 seconds...
And now container management is accessible. Thanks for the help, and TIL about how docker does(n't) apply supplementary groups to a container.

Did you find this page helpful?