Seahub does not always start automatically within a Docker container after a system reboot

Seahub does not always start automatically within a Docker container after a system reboot, even though the restart: unless-stopped directive is specified in the seafile-server.yml file.
Seafile is running, also the notification server, but Seahub is not.

My Solutions:
Restarting the container does not help; it must be destroyed and recreated.
The other option is to start Seahub inside the container using docker exec. This always works.
What do I need to do to ensure that Seahub is always running once the container is back up and running after a reboot?

Thanks for reporting the issue. We will check whether we can reproduce the problem once we have time.