Closed klangborste closed 1 year ago
docker logs
show not really something helpful for diagnosis and also internally I was not able to find a place where the logs from apache are expected.
There is a fix on the way for this but for now
docker exec -ti CONTAINER_NAME chown -R www-kimai /opt/kimai/var
Thanks for the super fast reply.
For me an
docker exec -ti kimai chown -R www-kimai: /opt/kimai/var
docker exec -ti kimai apachectl -k restart
still fails with 500 internal error.
New images are now built and pushed (including multiarch). I'll close this for now, please open a new ticket if issues persist.
kimai2:apache is running fine again, thanks!
Describe the bug After the last update from the kimai apache image with the tag "apache2" and the image name "kimai/kimai2:apache" I get again an 500 internal server error. After a rollback to the container image https://hub.docker.com/layers/kimai/kimai2/apache-1.30.6-prod/images/sha256-aeda8a97c08e2a04e27a0d9277215f4061dd27c92daccb337cb9ae171adc8694?context=explore it works fine again.
To Reproduce Steps to reproduce the behaviour:
Server
Command used to run the container
Docker compose file (with passwords redacted)
Additional context Perhaps it belongs to the ticket what I had already set once: https://github.com/kimai/kimai/issues/3788