I don't have much time to dig into this further at the moment, but I believe getting clarity from bitwarden support would be best to know the appropriate way for logrotate to work. rwxr-xr-x 1 nobody nogroup 0 Apr 2 15:30 error.log rwxr-xr-x 1 nobody nogroup 93 Apr 2 15:30 access.log Should see an output ls -al /var/log/nginx/ĭrwxr-xr-x 2 nobody nogroup 4096 Apr 2 15:30. Run command `docker cp logrotate.sh bitwarden-nginx:/`Ĭonnect to your container `docker exec -it bitwarden-nginx bash`Ĭheck for file rotation `ls -al /var/log/nginx` I also tested their script (logrotate.sh) which does work if you want to manually add them to your container In regard to a long term fix, I think it might be worth asking in the bitwarden github or forums to get some additional clarity on how logrotate should work.

A quick manual fix would be to shrink those files down to free up some space. The logs are mounted from the container to your local xpenology bwdata/logs folder. Not sure why it's not there, but seems there is a few different things going on with how logrotate should be done. I noticed here there is another logrotate.sh script (which is not on my container). I checked my bwdata/logs/nginx/access.log and I do see some really old entries.Ĭhecking on the nginx container I do see /etc/logrotate.d/nginx config file to rotate the logs but the logrotate command is not found (which could explain why we're not seeing the rotation occur. I'm assuming you're referring to the bwdata/logs/ folders?

Bitwarden free self hosted