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

[biggt]

Eventually, over time, the Vikunja app crashes and the status shows that it's going to restart but never does.

I don't know how to duplicate this issue, other than just waiting... it's now done this two or three days in a row now...

2025-02-06T18:49:11Z: WEB       ▶ 10.0.3.250  GET 200 /api/v1/notifications?page=1 2.714438ms - Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
2025-02-06T18:50:12Z: WEB       ▶ 10.0.3.250  GET 200 /api/v1/notifications?page=1 3.117954ms - Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
2025-02-06T18:52:24Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:24Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:25Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:25Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:27Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:27Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:29Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:29Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:31Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:31Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:34Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:34Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:38Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:38Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:46Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:46Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:52:59Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:52:59Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:53:25Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:53:26Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:54:17Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:54:17Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:55:18Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:55:18Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:56:18Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:56:18Z: CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving
2025-02-06T18:57:19Z: INFO      ▶ 001 No config file found, using default or config from environment variables.
2025-02-06T18:57:24Z: CRITICAL  ▶ 002 dial tcp: lookup redis: i/o timeout

Now, I don't specify my config file as a file, but instead specify environment variables inside the docker container. This appears to be working just fine... until randomly it crashes (maybe due to inactivity?)

services:
  vikunja:
    image: vikunja/vikunja
    container_name: vikunja_app
    environment:
      VIKUNJA_SERVICE_PUBLICURL: https://vikunja.domain.com
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: redacted
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: redacted
      VIKUNJA_REDIS_ENABLED: 1
      VIKUNJA_REDIS_HOST: 'redis:6379'
      VIKUNJA_CACHE_ENABLED: 1
      VIKUNJA_CACHE_TYPE: redis
      VIKUNJA_SERVICE_ENABLEREGISTRATION: false
      VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: true
      VIKUNJA_MAILER_ENABLED: true
      VIKUNJA_MAILER_HOST: mail.redacted.com
      VIKUNJA_MAILER_PORT: 587
      VIKUNJA_MAILER_AUTHTYPE: login
      VIKUNJA_MAILER_USERNAME: [email protected]
      VIKUNJA_MAILER_PASSWORD: redacted
      VIKUNJA_MAILER_FROMEMAIL: [email protected]
    ports:
      - 3456:3456
    volumes:
      - ./files:/app/vikunja/files
#      - ./config/config.yml:/etc/vikunja/config.yml
    depends_on:
      db:
        condition: service_healthy
    restart: unless-stopped

  db:
    image: mariadb:10
    container_name: vikunja_db
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      MYSQL_ROOT_PASSWORD: redacted
      MYSQL_USER: vikunja
      MYSQL_PASSWORD: redacted
      MYSQL_DATABASE: vikunja
    volumes:
      - ./db:/var/lib/mysql
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "mysqladmin ping -h localhost -u $$MYSQL_USER --password=$$MYSQL_PASSWORD"]
      interval: 2s
      start_period: 30s

  redis:
    container_name: vikunja_redis
    image: redis

[kolaente]

This line:

CRITICAL  ▶ 002 dial tcp: lookup redis on 127.0.0.11:53: server misbehaving

seems to indicate a problem with your redis server. What's in the logs of it?