[Bug]: planka not writing logs #628

New Issue

OVERLORD · 2026-02-04T20:37:03+03:00

OVERLORD commented

2026-02-04 20:37:03 +03:00

Originally created by @WirtsLegs on GitHub (Jan 11, 2025).

Where is the problem occurring?

Docker Swarm deployment

What browsers are you seeing the problem on?

N/A

Current behaviour

planka.log is created but remains empty regardless of if it is mounted to the host or internal to the container, suspect the lack of logs is somehow tied to OIDC being enabled as I was getting some logs via docker logs command prior to enabling it, since enabling that docker logs returns nothing and planka.log is empty

Desired behaviour

planka.log should contain logs

Steps to reproduce

Stand up planka on docker swarm with the following compose (note sensitive bits obviously redacted)

services:
  planka:
    image: ghcr.io/plankanban/planka:latest
    restart: on-failure
    volumes:
      - /mnt/appdata/planka/user-avatars:/app/public/user-avatars
      - /mnt/appdata/planka/project-background-images:/app/public/project-background-images
      - /mnt/appdata/planka/attachments:/app/private/attachments
      - /mnt/appdata/planka/logs:/app/logs
    ports:
      - 3948:1337
    environment:
      - BASE_URL=<baseurl>
      - DATABASE_URL=postgresql://postgres@postgres/planka
      - SECRET_KEY=<secret>
      - OIDC_ISSUER=<issuer url>
      - OIDC_CLIENT_ID=planka
      - OIDC_CLIENT_SECRET=<secret>
      - OIDC_ADMIN_ROLES=Admins
      - OIDC_SCOPES=openid email profile
      - OIDC_IGNORE_ROLES=false
    depends_on:
      - postgres

  postgres:
    image: postgres:16-alpine
    restart: on-failure
    volumes:
      - /mnt/appdata/planka/db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=planka
      - POSTGRES_HOST_AUTH_METHOD=trust
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres -d planka"]
      interval: 10s
      timeout: 5s
      retries: 5

Other information

I have seen https://github.com/plankanban/planka/issues/738 and https://github.com/plankanban/planka/issues/850

in both cases the issue was resolved via chowning the log folder, I have attempted to mount to a directory and ensured it was owned by 1000:1000 with no change. The planka.log file is being created so it has access but the file remains empty.

Originally created by @WirtsLegs on GitHub (Jan 11, 2025). ### Where is the problem occurring? Docker Swarm deployment ### What browsers are you seeing the problem on? N/A ### Current behaviour planka.log is created but remains empty regardless of if it is mounted to the host or internal to the container, suspect the lack of logs is somehow tied to OIDC being enabled as I was getting some logs via docker logs command prior to enabling it, since enabling that docker logs returns nothing and planka.log is empty ### Desired behaviour planka.log should contain logs ### Steps to reproduce Stand up planka on docker swarm with the following compose (note sensitive bits obviously redacted) ```YAML services: planka: image: ghcr.io/plankanban/planka:latest restart: on-failure volumes: - /mnt/appdata/planka/user-avatars:/app/public/user-avatars - /mnt/appdata/planka/project-background-images:/app/public/project-background-images - /mnt/appdata/planka/attachments:/app/private/attachments - /mnt/appdata/planka/logs:/app/logs ports: - 3948:1337 environment: - BASE_URL=<baseurl> - DATABASE_URL=postgresql://postgres@postgres/planka - SECRET_KEY=<secret> - OIDC_ISSUER=<issuer url> - OIDC_CLIENT_ID=planka - OIDC_CLIENT_SECRET=<secret> - OIDC_ADMIN_ROLES=Admins - OIDC_SCOPES=openid email profile - OIDC_IGNORE_ROLES=false depends_on: - postgres postgres: image: postgres:16-alpine restart: on-failure volumes: - /mnt/appdata/planka/db-data:/var/lib/postgresql/data environment: - POSTGRES_DB=planka - POSTGRES_HOST_AUTH_METHOD=trust healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres -d planka"] interval: 10s timeout: 5s retries: 5 ``` ### Other information I have seen https://github.com/plankanban/planka/issues/738 and https://github.com/plankanban/planka/issues/850 in both cases the issue was resolved via chowning the log folder, I have attempted to mount to a directory and ensured it was owned by 1000:1000 with no change. The planka.log file is being created so it has access but the file remains empty.

OVERLORD added the help wanted label 2026-02-04 20:37:03 +03:00

OVERLORD commented

2026-02-04 20:37:10 +03:00

@Knatschsack commented on GitHub (Jan 14, 2025):

Same for me with docker compose. Can see docker logs and docker compose logs for planka database but no output for planka webservice. the logfile in the container exists but remains empty.

@Knatschsack commented on GitHub (Jan 14, 2025): Same for me with docker compose. Can see docker logs and docker compose logs for planka database but no output for planka webservice. the logfile in the container exists but remains empty.

OVERLORD commented

2026-02-04 20:37:13 +03:00

@Morriz commented on GitHub (Apr 22, 2025):

why is help needed @meltyshev ? You can just output to both logs and stdout+stderr with tee...

@Morriz commented on GitHub (Apr 22, 2025): why is help needed @meltyshev ? You can just output to both logs and stdout+stderr with `tee`...

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#628