Uptime-Kuma giving me permission denied on Docker daemon socket

I’m using the “admin” user on my TrueNAS Scale ElectricEel-24.10.2

I tried to deploy the uptime-kuma container from “Discover Apps”.
There isn’t really much to configure, except the directory for uptime-kuma config.

I then try to start the container but it just loops in restarts until it finally stops.

Checking docker ps in the shell shows me more info.

In the shell I then type:
docker logs --tail 100 -f c4bc92d0afe7

result:
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.46/containers/c4bc92d0afe7/json": dial unix /var/run/docker.sock: connect: permission denied

$ ls -lah /var/run/docker.sock

srw-rw---- 1 root docker 0 Feb 9 22:15 /var/run/docker.sock

Interesting enough, I have an older TrueNAS Scale machine, which I also upgraded to ElectricEel-24.10.2, but on that one I’m using the user “root” and I have no issue there with uptime-kuma.

What leads me to suspect that something is up with the usernames.


How can I fix this?

Can you post what your configuration of the actual app looks like? I just tried installing using an iXvolume, not logged in a root, and it came up no problem, which makes me suspect a configuration error.

The permission denied error is for accessing the docker logs. You just need to use sudo before that docker command.

And that Runs As Context widget refers to the container run as user, so which account you use to access the UI is not relevant.

What I didn’t mention is, I have already been running uptime-kuma in Dragonfish as a custom docker app.
I upgraded my TrueNAS Scale to ElectricEel, but for some reason uptime-kuma didn’t work anymore.

I decided to delete that docker app, and get the one from the “Discovery Apps”.

here is the log from that one:

Welcome to Uptime Kuma
Your Node.js version: 20.18.0
2025-02-10T16:49:42Z [SERVER] INFO: Env: production
2025-02-10T16:49:42Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.1
2025-02-10T16:49:42Z [SERVER] INFO: Loading modules
2025-02-10T16:49:43Z [SERVER] INFO: Creating express and socket.io instance
2025-02-10T16:49:43Z [SERVER] INFO: Server Type: HTTP
2025-02-10T16:49:43Z [SERVER] INFO: Custom hostname: 0.0.0.0
2025-02-10T16:49:43Z [SERVER] INFO: Data Dir: ./data/
2025-02-10T16:49:43Z [SETUP-DATABASE] INFO: UPTIME_KUMA_DB_TYPE is provided by env, try to override db-config.json
2025-02-10T16:49:43Z [DB] INFO: Database Type: sqlite
2025-02-10T16:49:43Z [SERVER] INFO: Connected to the database
2025-02-10T16:49:43Z [DB] WARN: Aggregate table migration is already in progress, or it was interrupted
2025-02-10T16:49:43Z [DB] ERROR: Database migration failed
2025-02-10T16:49:43Z [SERVER] ERROR: Failed to prepare your database: Aggregate table migration is already in progress

Looks like something went wrong during the transition to ElectricEel.
No worries I just delete the folder for uptime-kuma and set it up from scratch.

I’ll report back if thats not working.

Deleting the folder content of uptime-kuma resolved the issue. It will take me a few minutes to configure it back, but that’s ok.

Issue resolved as far as I’m concerned.

2 Likes