Seafile 13 docker logrotate problem

Good afternoon, the log rotation in Seafile 13.0.24 is not working. How can this be fixed?

seafile/logs$ ll

– 4,7G

-rw-rw-rw-+ 1 root root 4,6K авг 19 14:14 enterpoint.log

-rw-rw-rw-+ 1 8000 8000 0 июн 1 15:15 file_updates_sender.log

-rw-rw-rw-+ 1 root root 194K сен 9 04:54 logrotate.log

-rw-rw-rw-+ 1 8000 8000 0 июн 1 15:15 onlyoffice.log

-rw-r–r–+ 1 www-data root 0 июн 1 15:15 seafdav.access.log

-rw-r–r–+ 1 www-data root 0 июн 1 15:15 seafdav.error.log

-rw-rw-rw-+ 1 8000 8000 39K сен 9 16:44 seafevents.log

-rw-rw-rw-+ 1 8000 8000 181K авг 4 04:49 seafevents.log.2026-07-28

-rw-rw-rw-+ 1 8000 8000 187K авг 11 04:36 seafevents.log.2026-08-04

-rw-rw-rw-+ 1 8000 8000 182K авг 18 04:36 seafevents.log.2026-08-11

-rw-rw-rw-+ 1 8000 8000 213K авг 25 04:44 seafevents.log.2026-08-18

-rw-rw-rw-+ 1 8000 8000 189K сен 1 04:44 seafevents.log.2026-08-25

-rw-rw-rw-+ 1 8000 8000 185K сен 8 04:44 seafevents.log.2026-09-01

-rw-r–r–+ 1 www-data root 238K сен 9 08:25 seafhttp.access.log

-rw-r–r–+ 1 www-data root 0 авг 19 11:14 seafhttp.error.log

-rw-rw-rw-+ 1 8000 8000 34K сен 3 13:06 seafile.log

-rw-rw-rw-+ 1 8000 8000 3,2M сен 9 17:01 seafile-monitor.log

-rw-r–r–+ 1 www-data root 4,7G сен 9 17:04 seahub.access.log

-rw-rw-rw-+ 1 8000 8000 0 авг 19 11:14 seahub_email_sender.log

-rw-r–r–+ 1 www-data root 20K сен 9 13:59 seahub.error.log

-rw-rw-rw-+ 1 8000 8000 2,1M сен 9 14:00 seahub.log

-rw-rw-rw-+ 1 8000 8000 0 июн 1 15:15 seasearch_index.log

Access rights to the log directory
drwxrwxrwx+ 2 root root 4,0K сен 8 05:14 logs/

Seafile is running in non‑root mode.
I saw the instruction Logrotate - Seafile Admin Manual
but it doesn’t work for docker, or you need to send restart commands to the container. Can someone suggest how to do this?

Thank you for reporting the issue.

The bug is related to non-root mode.

The bug has been fixed in non root logrotate by SkywalkerSpace · Pull Request #501 · haiwen/seafile-docker · GitHub

Do we need to update the Docker container, or how can we solve the problem in the running container?

You can wait until the next version of docker image is released for Seafile 13.0, then update the docker image.