Getting Api Error on installaing with docker compose

Support
1

I am installing vikunja with docker compose. my compose file looks like this

version: '3'

services:
  db:
    image: mariadb:10
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      MYSQL_ROOT_PASSWORD: supersecret
      MYSQL_USER: vikunja
      MYSQL_PASSWORD: secret
      MYSQL_DATABASE: vikunja
    volumes:
      - ./db:/var/lib/mysql
    restart: unless-stopped
    ports:
        - 3307:3306
  api:
    image: vikunja/api
    environment:
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: secret
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
      VIKUNJA_SERVICE_FRONTENDURL: http://192.168.2.45:8008/
    ports:
      - 3456:3456
    volumes:
      - ./files:/app/vikunja/files
    depends_on:
      - db
    restart: unless-stopped
  frontend:
    image: vikunja/frontend
    ports:
      - 8008:80
    environment:
      VIKUNJA_API_URL: http://192.168.2.45:3456/api/v1
    restart: unless-stopped

I am getting this error

2022/09/05 11:58:05 No config file found, using default or config from environment variables.
2022-09-05T11:58:05.503920442Z: CRITICAL        ▶ migration/Migrate 002 Migration failed: Error 1130: Host '192.168.96.4' is not allowed to connect to this MariaDB server

how to correct this?

2

Anything in the mariadb container logs?

If you don’t have any data in it yet I’d try to nuke the db container files and start again.

3

No config file found, using default or config from environment variables.

that looks relatively harmless, but you could change this by setting up a config file and mapping it to one of the configuration file paths documented here: Config options | Vikunja

:arrow_forward: migration/Migrate 002 Migration failed: Error 1130: Host ‘192.168.96.4’ is not allowed to connect to this MariaDB server

I think I got that issue during my first build of the server. The MariaDB image has a few things it does during its first launch. Does bringing the service down and back up once MariaDB is done with setup help any?