Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[BUG] Permissions of Influxdb folder do not follow PUID/PGID set in the docker-compose file #362

@garret

Description

@garret

I ran scrutiny with such docker-compose scheme on my raspberry pi 4b (4GB):

    scrutiny:
        cap_add:
            - SYS_RAWIO
        ports:
            - 8123:8080
        environment:
            - PUID=${PUID}
            - PGID=${PGID}
            - TZ=${TIMEZONE}
        volumes:
            - /run/udev:/run/udev:ro
            - ${CONFIG_FOLDER}/scrutiny/config:/opt/scrutiny/config
            - ${CONFIG_FOLDER}/scrutiny/influxdb:/opt/scrutiny/influxdb
        devices:
            - /dev/sdb
        container_name: scrutiny
        restart: unless-stopped
        image: ghcr.io/analogj/scrutiny:master-omnibus

Since it was introduced the influxdb database I now encounter the issue that the /opt/scrutiny/influxdb folder is not locally saved after my PUID and PGID settings (set in an .env file next to my docker-compose file). That is not the case for the /opt/scrutiny/config folder which instead respects the PUID and PGID settings.

I tried adding user: ${PUID}:${PGID} in the docker-compose but in that way scrutiny does not event start.

Do you know how to solve such issue?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions