Docker containers still not starting on reboot

Seafile Server
1

In this post from over a year ago, I reported that the Seafile docker containers don’t restart after reboot:

So as I really need to get my home set-up moved off CentOS v7, I’ve revisited the instructions and followed them to the letter:

Setup pro edition - Seafile Admin Manual

However, the same issue - the docker contains aren’t restarting on reboot due to restart: unless-stopped missing from the composer files.

I notice that since I last looked at Seafile docker, that the composition structure has changed from the single composer.yml file into three: caddy.yml, seadoc.yml and seafile-server.yml.

Interestingly, the single service in caddy.yml does have the above line so restarts as expected. If the caddy container supposed to start the other services? If so, then it’s not working. So you have to add the restart line to the other two composer files. NOTE: there are multiple serviecs in seafile-server.yml - you have to add restart to each section. Then re-run docker compose up -d.

I’ve scoured the documentation for any mention of this so surely, I must be missing something??

2

Thanks for reporting the issue. We will give it a check in this week.

3

@Rob_Nicholson here you can find the information about different auto start methods and how to enable them…

Seafile Docker autostart - Seafile Admin Manual

4

There should be at a reference to that article from the main installation article. But won’t 99% of installations want the docker starting automatically?

5

It is fixed now: 12.0 add restart: unless-stopped by SkywalkerSpace · Pull Request #596 · haiwen/seafile-admin-docs · GitHub

1 Like
6

Smashing, that’ll help people in future :slight_smile:

7

Goodness, when you said it was fixed, I kind of assume it was in the next release but I’ve just provisioned another docker test and the lines are there :wink: