Database locked when using remote (NAS) volume for config

[mgrimace]

Hello,

I'm a new user and trying to setup Mealie for the first time. No matter what group name I enter, including random names/digits it gives me the error group name is taken. I'm using the single container build with the compose file below. Note I have an SMB/CIFS NAS mounted for the /app/data, and attempted to change the port to 9925 to access the webui since 3000 was already taken by gethomepage.dev.

Thanks in advance for any help!

---
version: "3.7"
services:
  mealie-omni:
    image: hkotel/mealie:omni-nightly
    container_name: mealie
    ports:
      - 9925:3000
      - 9924:9000
    volumes:
      - /mnt/media/media/recipes:/app/data/
    environment:
      - ALLOW_SIGNUP=true
      - PUID=1000
      - PGID=1000
      - TZ=America/Toronto
      - BASE_URL=https://mealie.mydomain.com
    networks:
      - homelab
    restart: unless-stopped
    security_opt:
      - apparmor:unconfined

networks:
  homelab:
    driver: bridge
    external: true

[mgrimace]

Added the API port as well, since Authentik is already using port 9000.

[mgrimace]

I also tried the default credentials instead of trying to create a new account at the webUI initial screen, and I get the error something went wrong with changeme@email.com and MyPassword.

[mgrimace]

Interestingly, if I revert to the default mealie-data:/app/data and re-add

volumes:
  mealie-data:
    driver: local

I can log in using the default values, I'm missing something in my compose when using a mounted drive (note that the mounted NAS does work for other containers such as sonarr, radarr, etc.). When I do use /mnt/media/recipes and check the location, there do appear to be all the database/files, etc. Any advice is appreciated

[mgrimace]

Ok, using a mounted drive for the config locks the database as in this issue: #2409
The login issue I've described a symptom of the locked database.