First setup with unified container sqlite

Support
1

I have a running setup from a while ago where the docker setup was still with a vikunja/api and vikunja/frontend and there I have no problems, but with the vikunja/vikunja integrated image I get permission problems. I’m following Full docker example | Vikunja

version: '3'

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_JWTSECRET: pjicf9Cs8KjNjV
      VIKUNJA_SERVICE_PUBLICURL: http://localhost:3456/
      # Note the default path is /app/vikunja/vikunja.db.
      # This config variable moves it to a different folder so you can use a volume and 
      # store the database file outside the container so state is persisted even if the container is destroyed.
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
    ports:
      - 3456:3456
    volumes:
      - ./files:/app/vikunja/files
      - ./db:/db
    restart: unless-stopped

I did

mkdir $PWD/files $PWD/db
chown 1000 $PWD/files $PWD/db

but get permission error on starting even though the files are owned by 1000

vikunja-vikunja-1  | info: creating the new user vikunja with 1000:1000
vikunja-vikunja-1  | usermod: no changes
vikunja-vikunja-1  | 2024-03-20T12:05:51.412579305Z: INFO       ▶ config/InitConfig 001 No config file found, using default or config from environment variables.
vikunja-vikunja-1  | 2024-03-20T12:05:51.413096055Z: CRITICAL   ▶ migration/initMigration 002 Could not connect to db: could not open database file [uid=1000, gid=1000]: open /db/vikunja.db: per

Any idea what I’m doing wrong?

2

Okay, eventhough user 1000 owns the files, vikunja creates vikunja.db with no permissions by default, chmod u+rw db/vikunja.db fixes it.