After updating to 0.20.0 no login (user does not exist)

Do you get any messages like “Could not connect to db: could not open database file [uid=1001, gid=1001]: open ./vikunja.db: is a directory” when you run docker-compose up?

I’m trying to launch a version of this on my machine, but it looks like you’re trying to mount a folder as /app/vikunja/vikunja.db. This may reflect how you capture most databases (I’ll include mine for reference. It uses MySQL.), but an sqlite database is a file. you’d want to mount it the same way you would the config files, but with rw instead of ro.

Promised reference:

version: '2'
services:
  db:
    image: mariadb:10
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      MYSQL_ROOT_PASSWORD: imgladthispasswordisloggedinplaintext
      MYSQL_USER: vikunja
      MYSQL_PASSWORD: ifihadtomakeapassword
      MYSQL_DATABASE: vikunja
    volumes:
      - ./db:/var/lib/mysql
  api:
    image: vikunja/api:latest
    environment:
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: <password>
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_SERVICE_FRONTENDURL: https://localhost:3456/
    volumes:
      - ./data:/app/vikunja/files
    ports:
      - 3456:3456
    depends_on:
      - db
    restart: on-failure
  frontend:
    image: vikunja/frontend:latest
    ports:
      - 80:80
    environment:
      VIKUNJA_API_URL: http://localhost:3456/api/v1
    restart: always