Skip to content

[bug] Config.json not persistent across docker recreation #997

Description

@Wizard0f0zz

Description of the bug

config.json is not persistent across docker down and up commands

Step by step instructions to reproduce the bug

BEFORE RESTART
$ ls -ltr /homepath/filestash/data/state/config/config.json
-rw-rw---- 1 1000 1000 2784 Jun 20 21:57 /homepath/filestash/data/state/config/config.json

COMPOSE VOLUME
volumes:
- /homepath/filestash/data/state:/app/data/state
- /mnt/media:/media

RUN
docker compose down filestash
docker compose up -d filestash

AFTER RESTART
$ ls -ltr /homepath/filestash/data/state/config/config.json
-rw-rw---- 1 1000 1000 975 Jun 20 21:58 /homepath/filestash/data/state/config/config.json

NOTE: Notice the size changing from 2784 bytes to 975 bytes.
I have to go through the whole admin setup again after this.

Can you replicate that error from the demo?

No, requires docker container access

Observed behavior

config.json resets everytime you run
docker compose down filestash
docker compose up -d filestash

Expected behavior

config.json to remain persistent across docker down and up commands

ADDITIONAL INFORMATION:

docker installation on TrueNas Scale v26.0.0-BETA.1
Docker compose
filestash:
image: machines/filestash:latest
container_name: filestash
restart: unless-stopped
networks:
- dock_lan
volumes:
# - /homepath/filestash/data/state/config/config.json:/app/data/state/config/config.json
- /homepath/filestash/data/state:/app/data/state
- /mnt/media:/media
environment:
- TZ=${TZ}
- APPLICATION_URL=https://filestash.mydomain.com
labels:
- traefik.enable=true
# HTTPS Router
- traefik.http.routers.filestash.rule=Host(filestash.mydomain.com)
- traefik.http.routers.filestash.entrypoints=websecure
- traefik.http.routers.filestash.tls=true
- traefik.http.services.filestash.loadbalancer.server.port=8334

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions