You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Add a writable volume in docker-compose.yml to /app/logs:
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
The text was updated successfully, but these errors were encountered:
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:
docker-compose.yml
to/app/logs
: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:
Additional context:
/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
The text was updated successfully, but these errors were encountered: