starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-24 19:08:59 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

[Bug]: Container restarting without any log #769

New Issue
Closed
opened 2026-02-04 21:16:43 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 21:16:43 +03:00
Owner
Copy Link

Originally created by @AnthonyLELUYER on GitHub (Jul 29, 2025).

Where is the problem occurring?

I encountered the problem while interacting with the server (Backend)

What browsers are you seeing the problem on?

Firefox

Current behavior

Hello,
I'm trying to use the Docker deployment, here is my docker-compose:

secrets:
  database_password:
    file: "./secrets/database_password.secret"
  oidc_client_secret:
    file: "./secrets/oidc_client_secret.secret"
  secret_key:
    file: "./secrets/secret_key.secret"

services:
  planka:
    image: ghcr.io/plankanban/planka:2.0.0-rc.3
    restart: on-failure
    volumes:
      - favicons:/app/public/favicons
      - user-avatars:/app/public/user-avatars
      - background-images:/app/public/background-images
      - attachments:/app/private/attachments
    user: 1000:1000
    tmpfs:
      - /app/.tmp:mode=770,uid=1000,gid=1000
    ports:
      - 3000:1337
    environment:
      - BASE_URL=https://#######.fr
      - DATABASE_URL=postgresql://postgres:$${DATABASE_PASSWORD}@postgres/planka
      - DATABASE_PASSWORD__FILE=/run/secrets/database_password
      - SECRET_KEY__FILE=/run/secrets/secret_key
      - LOG_LEVEL=debug
      - DEFAULT_LANGUAGE=fr-FR
      - OIDC_ISSUER=https://######/realms/######
      - OIDC_CLIENT_ID=######
      - OIDC_CLIENT_SECRET__FILE=/run/secrets/oidc_client_secret
    secrets:
      - oidc_client_secret
      - database_password
      - secret_key
    networks:
      - proxy
      - planka
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:16-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
    networks:
      - planka

volumes:
  favicons:
  user-avatars:
  background-images:
  attachments:
  db-data:

networks:
  planka:
    internal: true
  proxy:
    external: true

The postgres container is healthy, however the planka container is restarting without any logs, the output of this command is empty:
docker logs planka-planka-1
Here is the docker ps command:
Image


### Desired behavior

_No response_

### Steps to reproduce

I followed the documentation here: https://docs.planka.cloud/docs/installation/docker/production-version
I :
- retrieved the docker-compose
- edited the env variables
- added my networks (the container is restarting without my networks)
- created the admin with the command provided by the doc
- executed the command `docker-compose up -d`
- found the issue

### Other information

_No response_
Originally created by @AnthonyLELUYER on GitHub (Jul 29, 2025). ### Where is the problem occurring? I encountered the problem while interacting with the server (Backend) ### What browsers are you seeing the problem on? Firefox ### Current behavior Hello, I'm trying to use the Docker deployment, here is my docker-compose: ``` secrets: database_password: file: "./secrets/database_password.secret" oidc_client_secret: file: "./secrets/oidc_client_secret.secret" secret_key: file: "./secrets/secret_key.secret" services: planka: image: ghcr.io/plankanban/planka:2.0.0-rc.3 restart: on-failure volumes: - favicons:/app/public/favicons - user-avatars:/app/public/user-avatars - background-images:/app/public/background-images - attachments:/app/private/attachments user: 1000:1000 tmpfs: - /app/.tmp:mode=770,uid=1000,gid=1000 ports: - 3000:1337 environment: - BASE_URL=https://#######.fr - DATABASE_URL=postgresql://postgres:$${DATABASE_PASSWORD}@postgres/planka - DATABASE_PASSWORD__FILE=/run/secrets/database_password - SECRET_KEY__FILE=/run/secrets/secret_key - LOG_LEVEL=debug - DEFAULT_LANGUAGE=fr-FR - OIDC_ISSUER=https://######/realms/###### - OIDC_CLIENT_ID=###### - OIDC_CLIENT_SECRET__FILE=/run/secrets/oidc_client_secret secrets: - oidc_client_secret - database_password - secret_key networks: - proxy - planka depends_on: postgres: condition: service_healthy postgres: image: postgres:16-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 networks: - planka volumes: favicons: user-avatars: background-images: attachments: db-data: networks: planka: internal: true proxy: external: true ``` The postgres container is healthy, however the planka container is restarting without any logs, the output of this command is empty: `docker logs planka-planka-1` Here is the `docker ps` command: <img width="1428" height="108" alt="Image" src="https://github.com/user-attachments/assets/8a3e0878-1dba-4955-99e5-04c9ea643dfa" /> ``` ### Desired behavior _No response_ ### Steps to reproduce I followed the documentation here: https://docs.planka.cloud/docs/installation/docker/production-version I : - retrieved the docker-compose - edited the env variables - added my networks (the container is restarting without my networks) - created the admin with the command provided by the doc - executed the command `docker-compose up -d` - found the issue ### Other information _No response_
OVERLORD commented 2026-02-04 21:17:02 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jul 30, 2025):

Hi! Hmm… I have a guess that it might be related to the use of Docker secrets, as it seems to fail before Node.js even starts. I'll try to reproduce this now.

@meltyshev commented on GitHub (Jul 30, 2025): Hi! Hmm… I have a guess that it might be related to the use of Docker secrets, as it seems to fail before Node.js even starts. I'll try to reproduce this now.
OVERLORD commented 2026-02-04 21:17:10 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jul 30, 2025):

Yep, I was able to reproduce it. I remembered this comment: https://github.com/plankanban/planka/issues/1222#issuecomment-3014050188 - if there's no newline at the end of each secret file, it fails silently.

For now, you can add an empty newline to the end of your secret files as a workaround. Already working on a fix.

@meltyshev commented on GitHub (Jul 30, 2025): Yep, I was able to reproduce it. I remembered this comment: https://github.com/plankanban/planka/issues/1222#issuecomment-3014050188 - if there's no newline at the end of each secret file, it fails silently. For now, you can add an empty newline to the end of your secret files as a workaround. Already working on a fix.
OVERLORD commented 2026-02-04 21:17:16 +03:00
Author
Owner
Copy Link

@AnthonyLELUYER commented on GitHub (Jul 30, 2025):

Thanks! The workaround fixed it

@AnthonyLELUYER commented on GitHub (Jul 30, 2025): Thanks! The workaround fixed it
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
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#769
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?