Dockge fails to start due to missing file in ./data

[Katherine1]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Followed installation steps.

1. Created /opt/dockge and /opt/stacks as root
2. Downloaded compose.yaml to /opt/dockge
3. Started dockge with docker-compose up -d

Rather than run as expected, Dockge creates the ./data directory, but then errors about a missing config .json in that directory. It looks like Dockge creates the data directory, but does not populate it so it fails when trying to open a file in that directory.

📝 Error Message(s) or Log

2024-11-18T01:32:07Z [SERVER] INFO: Welcome to dockge!
2024-11-18T01:32:07Z [SERVER] INFO: NODE_ENV: production
2024-11-18T01:32:07Z [SERVER] INFO: Server Type: HTTP
2024-11-18T01:32:07Z [SERVER] INFO: Data Dir: ./data/
2024-11-18T01:32:07Z [DB] WARN: ENOENT: no such file or directory, open 'data/db-config.json'
2024-11-18T01:32:07Z [SERVER] ERROR: Failed to prepare your database: EACCES: permission denied, open 'data/db-config.json'

🐻 Dockge Version

1.4.2

💻 Operating System and Arch

Fedora 40 x86

🌐 Browser

LibreWolf 132.0.2-1

🐋 Docker Version

Podman 5.2.3

🟩 NodeJS Version

No response

[mizady]

this sounds like it could be a permissions issue, have you tried a different directory or using chmod to verify that permissions are not an issue? I do this by running ls -l in the parent directory and look at the current permissions, then chmod 777 /opt/dockge/data or even perhaps /opt/dockge and try spinning it up again. it is not a good idea to leave the folder at 777 for security reasons so if this resolves the issue then you may need to chown the dockge directory to root or whatever user id that docker is attached to (default is root)

[mizady]

i tried to recreate the issue and sadly no luck. I've had this issue before and I don't recall what the cause was. have you tried changing the version tag from version 1? i use the latest tag when playing with dockge vanilla version so not sure if that has an impact. The command listed above does not include sudo, have you tried it using sudo docker compose up -d ? (also note the lack of - as well as that is technically a different executable that is now deprecated)

[Katherine1]

As I'm on Fedora, I have podman, not docker. I am currently using the version 1 tag. I'll try latest.

[mizady]

yea i noticed the os and podman after i replied. I hadn't worked with podman and its been a while for fedora so i may not get this one. I ran into the same problem on ubuntu server a few months back and i wiped it and used my modified version of dockge but then when i went to do it again it worked so i'm not 100% sure what I changed to fix it. If you want to try it to see if it'll work you're welcome to, it's based one the repository as of a few months ago but that was when node was still v18 not updated as it was recently. once the container buttons has been merged i'll be switching back to regular dockge. thejericko/dockge:latest is the tag for it on docker hub.

[Katherine1]

The version 1 tag and latest were last updated 10 months ago and seem to have the same build. The nightly tag was updated 1 month ago, so I tried that. No change.

[mizady]

alright hopefully someone with some podman experience will jump in here. I would try launching it as a podman command and not as a compose file to see if that works as well. perhaps --privileged maybe necessary