starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

Planka not logging #493

New Issue
Closed
opened 2026-02-04 19:55:15 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 19:55:15 +03:00
Owner
Copy Link

Originally created by @fcremer on GitHub (May 3, 2024).

Hello,

I am currently hosting Planka using Docker and have configured it with a docker-compose.yml file. I attempted to enable logging by adding a writable volume mapped to /app/logs and restarted the container. Unfortunately, Planka does not start logging.

Steps to reproduce:

  1. Add a writable volume in docker-compose.yml to /app/logs:
version: '3'

services:
  planka:
    image: ghcr.io/plankanban/planka:latest
    restart: on-failure
    volumes:
      - user-avatars:/app/public/user-avatars
      - project-background-images:/app/public/project-background-images
      - attachments:/app/private/attachments
      - logs:/app/logs
    ports:
      - 80:1337
    environment:
      - BASE_URL=https://xxxxx
      - DATABASE_URL=postgresql://postgres@postgres/planka
      - SECRET_KEY=xxxx



      - DEFAULT_ADMIN_EMAIL=xxxxx
      - DEFAULT_ADMIN_PASSWORD=xxxx
      - DEFAULT_ADMIN_NAME=xxxxx
      - DEFAULT_ADMIN_USERNAME=xxxxx
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:14-alpine
    restart: on-failure
    volumes:
      - 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

volumes:
  user-avatars:
  project-background-images:
  attachments:
  db-data:
  logs:
  1. Restart the Planka container.

Expected behavior:
I expected to see logs being written to planka.log within the mounted /app/logs directory.

Actual behavior:
No logs are being written to planka.log. The volume is mounted successfully and is writable, as verified by connecting to the container.

Environment:

  • Planka version: 1.17.2 (but same on older versions)
  • Docker version: 26.0.0 linux/arm64

Additional context:

  • Docker logs are also not showing any relevant output that might explain why logging isn't happening.
  • I have checked the permissions of the /app/logs directory and confirmed it is writable.

Could you provide any guidance on how to further investigate this issue or if there are additional configurations I might be missing?

Best regards,
Fabian

Originally created by @fcremer on GitHub (May 3, 2024). Hello, I am currently hosting Planka using Docker and have configured it with a docker-compose.yml file. I attempted to enable logging by adding a writable volume mapped to `/app/logs` and restarted the container. Unfortunately, Planka does not start logging. **Steps to reproduce**: 1. Add a writable volume in `docker-compose.yml` to `/app/logs`: ``` version: '3' services: planka: image: ghcr.io/plankanban/planka:latest restart: on-failure volumes: - user-avatars:/app/public/user-avatars - project-background-images:/app/public/project-background-images - attachments:/app/private/attachments - logs:/app/logs ports: - 80:1337 environment: - BASE_URL=https://xxxxx - DATABASE_URL=postgresql://postgres@postgres/planka - SECRET_KEY=xxxx - DEFAULT_ADMIN_EMAIL=xxxxx - DEFAULT_ADMIN_PASSWORD=xxxx - DEFAULT_ADMIN_NAME=xxxxx - DEFAULT_ADMIN_USERNAME=xxxxx depends_on: postgres: condition: service_healthy postgres: image: postgres:14-alpine restart: on-failure volumes: - 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 volumes: user-avatars: project-background-images: attachments: db-data: logs: ``` 2. Restart the Planka container. **Expected behavior**: I expected to see logs being written to `planka.log` within the mounted `/app/logs` directory. **Actual behavior**: No logs are being written to `planka.log`. The volume is mounted successfully and is writable, as verified by connecting to the container. **Environment**: - Planka version: 1.17.2 (but same on older versions) - Docker version: 26.0.0 linux/arm64 **Additional context**: - Docker logs are also not showing any relevant output that might explain why logging isn't happening. - I have checked the permissions of the `/app/logs` directory and confirmed it is writable. Could you provide any guidance on how to further investigate this issue or if there are additional configurations I might be missing? Best regards, Fabian
OVERLORD added the help wanted label 2026-02-04 19:55:15 +03:00
OVERLORD commented 2026-02-04 19:55:28 +03:00
Author
Owner
Copy Link

@mylesagray commented on GitHub (Jun 11, 2024):

Seeing the same, log volume mapped or not - in production or development mode there are no logs to volume or stdout.

@mylesagray commented on GitHub (Jun 11, 2024): Seeing the same, log volume mapped or not - in production or development mode there are no logs to volume or stdout.
OVERLORD commented 2026-02-04 19:55:35 +03:00
Author
Owner
Copy Link

@ipod86 commented on GitHub (Aug 15, 2024):

Same here

@ipod86 commented on GitHub (Aug 15, 2024): Same here
OVERLORD commented 2026-02-04 19:55:47 +03:00
Author
Owner
Copy Link

@vitobotta commented on GitHub (Aug 31, 2024):

Just came to say the same. There is no information in the log file at all for me.

@vitobotta commented on GitHub (Aug 31, 2024): Just came to say the same. There is no information in the log file at all for me.
OVERLORD commented 2026-02-04 19:55:52 +03:00
Author
Owner
Copy Link

@ipod86 commented on GitHub (Aug 31, 2024):

Maybe something from here will help

https://github.com/plankanban/planka/issues/850

@ipod86 commented on GitHub (Aug 31, 2024): Maybe something from here will help https://github.com/plankanban/planka/issues/850
OVERLORD commented 2026-02-04 19:55:55 +03:00
Author
Owner
Copy Link

@fcremer commented on GitHub (Sep 8, 2024):

Changing permission on the folder fixed it. Thanks you!

@fcremer commented on GitHub (Sep 8, 2024): Changing permission on the folder fixed it. Thanks you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#493
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?