error getting credentials on Raspberry Pi

[Snorbeard]

Hi! I tried to install it on my Raspberry Pi 5, but I get the error:
error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATH, out: ``
I don't have docker desktop on the raspberry, but do have the docker engine and compose. Is there a workaround? Saw people being able to run it on their Raspberry pi. Thnx in advance!

[adanb13]

Hi there,

Hmmm ,I did make a push today that helped with a missing library but this doesn't seem to be linked to that issue.

Are you able to pull other public images on your Raspberry Pi 5 without issues? Could you show what the Docker client config looks like?

Thanks

[Snorbeard]

Hi Adanb13, I could not get the error again after trying to replicate, but I still have the same bug as #22 and #23. I removed all the docker containers and used the following commands:
git clone https://github.com/log-forge/logforge.git
cd logforge
docker compose up -d --build
gives back error after pulling and starting containers:
[+] Running 8/8
✔ Network logforge_logforge-network Created
✔ Network logforge_default Created
✔ Container logforge-notifier Started
✔ Container logforge-autoupdate Started
✔ Container logforge-backend Started
✔ Container logforge-frontend Started
✘ Container logforge-alert-backend Error
✔ Container logforge-alert-frontend Created
dependency failed to start: container logforge-alert-backend is unhealthy

The logfiles in Logforge notifier. Logforge Backend and logforge-alert-backend
give the following error: while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory

[adanb13]

Could you try pulling down the stack then removing all of the images and then run docker compose up -d --build and pulling everything fresh and seeing if that works?

[mxklb]

@Snorbeard u must docker compose pull latest images, I think u simply missed that?

But I also have issues on raspberry pi (running ubuntu). I looks like the stack is not running as expected. I can't reach the frontend, so logforge on pi is actually useless. There are no docker logs pointing to any errors, so I don't know how to make it work. There must be some issues, maybe arm64 related, this is just a guess:

$ docker compose up -d --build
[+] Running 8/8
 ✔ Network logforge_logforge-network  Created                                                                                                                                                                   0.2s 
 ✔ Network logforge_default           Created                                                                                                                                                                   0.2s 
 ✔ Container logforge-autoupdate      Started                                                                                                                                                                   1.7s 
 ✔ Container logforge-backend         Started                                                                                                                                                                   1.8s 
 ✔ Container logforge-notifier        Started                                                                                                                                                                   1.7s 
 ✔ Container logforge-frontend        Started                                                                                                                                                                   2.9s 
 ✔ Container logforge-alert-backend   Healthy                                                                                                                                                                  28.4s 
 ✔ Container logforge-alert-frontend  Started                                                                                                                                                                  33.0s 

$ docker compose logs -f
logforge-notifier        | 2025-11-11 13:43:31 - [DEBUG] [bootstrap] Runtime data directory /app/data already populated; verifying essential files.
logforge-notifier        | 2025-11-11 13:43:31 - [INFO] [utils] using existing certificates
logforge-notifier        | 2025-11-11 13:43:32 - [INFO] [components] refreshing components: all
logforge-notifier        | 2025-11-11 13:43:32 - [INFO] [config] configuration loaded from /app/data/config.yaml
logforge-notifier        | 2025-11-11 13:43:32 - [INFO] [components] creating new app notifier
logforge-notifier        | 2025-11-11 13:43:32 - [INFO] [components] creating new notifier
logforge-notifier        | 2025-11-11 13:43:32 - [DEBUG] [components] match system updated
logforge-notifier        | 2025-11-11 13:43:32 - [INFO] [components] creating new notifier
logforge-notifier        | 2025-11-11 13:43:32 - [DEBUG] [components] match system updated
logforge-notifier        | INFO:     Started server process [8]
logforge-notifier        | INFO:     Waiting for application startup.
logforge-notifier        | INFO:     Application startup complete.
logforge-notifier        | INFO:     Uvicorn running on http://0.0.0.0:8085 (Press CTRL+C to quit)
logforge-backend         | Configuration Warnings:
logforge-backend         |    • Persistent storage disabled - alerts lost on restart
logforge-backend         | INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
logforge-backend         | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
logforge-backend         | INFO  [alembic.runtime.migration] Running stamp_revision  -> b1f3d6d5d5c2
logforge-backend         | INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
logforge-backend         | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
logforge-backend         | WARNI [app.config.alerts] Configuration Warnings:
logforge-backend         | WARNI [app.config.alerts]    • Persistent storage disabled - alerts lost on restart
logforge-backend         | [CORS] Configured origins: ['http://localhost:3008', 'http://localhost:3000', 'http://localhost:3001']
logforge-backend         | [Patch] Table 'containers' missing; skipping skip_checks patch until schema initialization runs
logforge-backend         | [Patch] Table 'containers' missing; skipping skip_checks patch until schema initialization runs
logforge-backend         | INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
logforge-backend         | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
logforge-backend         | INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
logforge-backend         | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
logforge-backend         | [WebSocket DEBUG] Starting connection for /ws/updates/all
logforge-backend         | [WebSocket DEBUG] WebSocket accepted for /ws/updates/all
logforge-backend         | [WebSocket DEBUG] Update type all is valid
logforge-backend         | [WebSocket DEBUG] Registering client for all
logforge-backend         | [WebSocket DEBUG] Client registered successfully for all
logforge-backend         | [WebSocket DEBUG] Sent connection confirmation for all
logforge-autoupdate      | time="2025-11-11T12:43:25Z" level=info msg="Watchtower 1.7.1"
logforge-autoupdate      | time="2025-11-11T12:43:25Z" level=info msg="Using no notifications"
logforge-autoupdate      | time="2025-11-11T12:43:25Z" level=info msg="Only checking containers using enable label"
logforge-autoupdate      | time="2025-11-11T12:43:25Z" level=info msg="Scheduling first run: 2025-11-12 00:43:25 +0000 UTC"
logforge-autoupdate      | time="2025-11-11T12:43:25Z" level=info msg="Note that the first check will be performed in 11 hours, 59 minutes, 59 seconds" 

P.S. I am running multiple other containers, so a general docker config on my pi must not be an issue. I have a tick stack running (influxdb, telegraf & grafana containers) which causes port conflicts (grafana also using port 3000). But even when simply stopping the tick stack (docker compose down), logforge doesn't show any frontend nor any frontend logs ..

[Snorbeard]

Hey, I figured I out! I had to search a lot of Google pages and docs, but I had once installed the docker desktop on my raspberry and removed it. There was a .docker directory with some files that gave the error of the credentials. After removing that directory, I could pull the image normally and it works. I can connect and interact with the webui on the host. Though I have an issue with connecting a different device, it's probably something on my side and not a bug. Thanks anyway for the help, and sorry for any inconvenience @mxklb Can you reach frontend on localhost:3008?

[mxklb]

Can you reach frontend on localhost:3008?

No I can't. As you see in the logs, there are no logforge-frontend container logs at all. so I have no idea why not working.

FYI: I have a headless approach, so docker desktop is not an option for my raspberry pi projects. Is it a dependency?

[adanb13]

Hi @Snorbeard glad to hear it's working! As for connecting form a different device, the docker-compose.yml currently binds to 127.0.0.1 at the following:

logforge/docker-compose.yml

Line 78 in 97f5819

- "127.0.0.1:${ALERT_ENGINE_FRONTEND_PORT:-3033}:3033"

logforge/docker-compose.yml

Line 34 in 97f5819

- "127.0.0.1:${NOTIFIER_WEB_PORT:-8087}:8085"

logforge/docker-compose.yml

Line 21 in 97f5819

- "127.0.0.1:${LOGFORGE_FRONTEND_PORT:-3008}:3000"

If you remove the bind and then start it up, it should bind to 0.0.0.0 (all interfaces) and be accessible from other devices on the network.

@mxklb I think I've identified an issue in the build process, will be updating it and pushing new image asap

[mxklb]

@adanb13 yes, thank you, removing the bind 127.0.0.1: from compose file I am able to access frontend from other device.

[adanb13]

I pushed a new image for the logforge-frontend as well, so it should startup correctly on the Raspberry Pi now also