Dashboard permission deleting geolite data (traefik-log-dashboard discussion #181)

:speech_balloon: GitHub discussion traefik-log-dashboard #181 in General, started by Splinter7914 on GitHub

Set this up today and its up an running and I see permission errors in the dashboard logs and wondering if these can be ignored? Or does this mean geo data will not work as expected?

running v2.4.1

dashboard is running as non root (same as quick start guide, but i run it as user 1000:1000). As we are only mounting /app/data then these errors are expected? Or is the quick start guide wrong in showing the container running as non root?

Also I am running agent as non root, it does have access to read traefik logs so I was curious if there could be other issues

WARNING: geolite2-redist/dbs-tmp is not writable. GeoIP lookups may fail.
This is usually a Docker permission issue. Rebuild the image to fix.
   ▲ Next.js 15.5.9
   - Local:        http://localhost:3000
   - Network:      http://0.0.0.0:3000

 ✓ Starting...
 ✓ Ready in 83ms
Fetching from agent [titan]: http://traefik-log-agent:5000/api/logs/access?position=-1&lines=1000&tail=false
[Error: EACCES: permission denied, rmdir '/app/node_modules/geolite2-redist/dbs-tmp'] {
  errno: -13,
  code: 'EACCES',
  syscall: 'rmdir',
  path: '/app/node_modules/geolite2-redist/dbs-tmp'
}
 ⨯ unhandledRejection:  [Error: EACCES: permission denied, rmdir '/app/node_modules/geolite2-redist/dbs-tmp'] {
  errno: -13,
  code: 'EACCES',
  syscall: 'rmdir',
  path: '/app/node_modules/geolite2-redist/dbs-tmp'
}
[Error: EACCES: permission denied, rmdir '/app/node_modules/geolite2-redist/dbs-tmp'] {
  errno: -13,
  code: 'EACCES', …

---
💬 Join in here or [on GitHub](https://github.com/hhftechnology/traefik-log-dashboard/discussions/181).
<!-- hhf-forum-sync -->

Splinter7914 commented on GitHub:

It works when I run the container as root and I had to make sure the path dashboard is writing to is owned by root with 777 permissions. Not sure if this is expected. It would be neat if we can get this to work for non root setup.

hhftechnology commented on GitHub:

@​Splinter7914
External Image
https://traefik-log-dashboard.hhf.technology/docs/troubleshooting#docker-issues

Splinter7914 replied in a thread on GitHub to hhftechnology:

Thanks that fixed it.

It might be good to add a note in the quick start that if running as a different user to set the directory ownership still to 1001. On my other container usually the user override works where the local paths are owned by the the user specified in the compose file. For example in my compose its running as user 1000:1000 and the files are written as user 1001.