Wrong permissions on app.conf prevent start of NetAlertX when using docker

[git24chris]

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://jokob-sk.github.io/NetAlertX/

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Edge
• Safari (unsupported) - PRs welcome
• N/A - This is an issue with the backend

Current Behavior

Installation: Proxmox-Server (V9, Trixie) -> LXC (Debian Trixie) -> Docker with Portainer-Agent -> Portainer GUI -> deploy portainer-default-yaml using bind mounts (with access rights as per documentation).

ATTENTION: Read permission denied.
    The application cannot read from "/data/config/app.conf". This will cause
    unpredictable errors. Please correct the file system permissions.

default by container deployment:
-------r-- 1 20211 20211 3963 18. Dez 20:57 app.conf (permission 004?)

should be? (at least it works that way)
-rw-r--r-- 1 20211 20211 160367 18. Dez 21:33 app.conf (permission 644)

Expected Behavior

Well, since you're setting the file during initialization, I would expect it to be correct from the start. Thanks.

Steps To Reproduce

Simply setup a NetAlerX instance using Portainer and the proposed default yaml.

Relevant app.conf settings

docker-compose.yml

What installation are you running?

Production (netalertx)

Debug or Trace enabled

• I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.

Relevant app.log section

  PASTE LOG HERE. Using the triple backticks preserves format. 

Docker Logs

  PASTE DOCKER LOG HERE. Using the triple backticks preserves format. 

[jokob-sk]

Hi,

did you follow the permissions docs?

https://jokob-sk.github.io/NetAlertX/docker-troubleshooting/file-permissions/?h=permi

The correct ownership of the files is a requirement for proper installation.

FYI @adamoutler not sure if we can make this clearer

[git24chris]

Yes, I created the path structures for the database and config, applied permissions as described in the documentation, set up bind mounts, and after all of that, deployed the stack.

However, the problem I encounter is caused by the container's init: the file should be generated within the structure with the correct file permissions during creation. The path permissions were set beforehand and are correct. Your question concerns directory permissions, but my issue involves the permissions of the app.conf file (see my "screenshot" mentioned in the problem statement).

The documentation is very clear. Please carefully review how the app.conf is generated; you are setting the wrong permissions on the file.

[adamoutler]

This should be working if you remove any users from docker compose now. if you need a specific user, use PUID/GUID environmental variables.

[jokob-sk]

Releasing -> Closing