Docker Self-Hosted Migration failed lookup db no such host, unable to find the IP address for the container \"/vikunja\"

Support
4

Update:

I added my VNET to the db, which fixed the issue of failed migration.

  vikunja_db:
    image: postgres
    container_name: vikunja_db
    environment:
      POSTGRES_PASSWORD: changeme
      POSTGRES_USER: vikunja
    volumes:
      - ./db:/var/lib/postgresql/data
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -h localhost -U $$POSTGRES_USER"]
      interval: 2s
    networks:
      - "personal_vnet"

At least Vikunja now starts up. However, now I’m getting new erors:
502 Bad Gateway error="dial tcp 172.20.0.8:3535: connect: connection refused"

I commented 2 lines:

      #VIKUNJA_SERVICE_PUBLICURL: https://vikunja.$DOMAINNAME
      #- "traefik.docker.network=pjvd_vnet"

and changed the order of these two:

      - "traefik.http.routers.vikunja.entrypoints=https"
      - "traefik.http.routers.vikunja.rule=Host(`vikunja.$DOMAINNAME`)"

In the Vikunja service.

These didn’t do the trick - however I noticed these lines in the Docker CLI:

vikunja     | 2024-12-30T19:31:38Z: INFO        ▶ 06a Ran all migrations successfully.
vikunja     | 2024-12-30T19:31:38Z: INFO        ▶ 06b Mailer is disabled, not sending reminders per mail
vikunja     | 2024-12-30T19:31:38Z: INFO        ▶ 06c Mailer is disabled, not sending overdue per mail
vikunja     | 2024-12-30T19:31:38Z: INFO        ▶ 06d Vikunja version v0.24.6
vikunja     | ⇨ http server started on [::]:3456

Changing
- "traefik.http.services.vikunja-svc.loadbalancer.server.port=8080"
to
- "traefik.http.services.vikunja-svc.loadbalancer.server.port=3456"
fixed the issue. Somewhere this port is defined, maybe as some hardcoded value as it’s the same port number found in Vikunja’s own docker example. At any rate I can now use Vikunja from a self-hosted solution!