gotenberg container does not start on reboot

[gioman]

I used the "docker+database" example to deploy solidtime and noticed that upon a reboot of the server the gotenberg container does not start (or better it exists)

docker ps -a
CONTAINER ID   IMAGE                        COMMAND                  CREATED       STATUS                             PORTS                                                                             NAMES
e1ad094f1607   solidtime/solidtime:latest   "start-container"        2 hours ago   Up 15 seconds (health: starting)   80/tcp, 443/tcp, 2019/tcp, 443/udp, 0.0.0.0:8000->8000/tcp, [::]:8000->8000/tcp   solidtime-app-1
01053d97f761   solidtime/solidtime:latest   "start-container"        2 hours ago   Up 15 seconds (health: starting)   80/tcp, 443/tcp, 2019/tcp, 8000/tcp, 443/udp                                      solidtime-scheduler-1
94d7fdfd3baa   solidtime/solidtime:latest   "start-container"        2 hours ago   Up 15 seconds (health: starting)   80/tcp, 443/tcp, 2019/tcp, 8000/tcp, 443/udp                                      solidtime-queue-1
05e68512e1e4   gotenberg/gotenberg:8        "/usr/bin/tini -- go…"   2 hours ago   Exited (0) 28 seconds ago                                                                                            solidtime-gotenberg-1
b3a112fb8bb5   postgres:15                  "docker-entrypoint.s…"   2 hours ago   Up 15 seconds (health: starting)   5432/tcp                                                                          solidtime-database-1
d2cccf73b84f   solidtime/solidtime:latest   "start-container php…"   9 hours ago   Exited (0) 9 hours ago                                                                                               solidtime-scheduler-run-37a835832e84

But then issuing a docker compose down and docker compose up -d makes things start as expected

docker compose down
[+] Running 6/6
 ✔ Container solidtime-queue-1      Removed                                                                                                             0.9s 
 ✔ Container solidtime-gotenberg-1  Removed                                                                                                             0.0s 
 ✔ Container solidtime-app-1        Removed                                                                                                             6.4s 
 ✔ Container solidtime-scheduler-1  Removed                                                                                                             0.8s 
 ✔ Container solidtime-database-1   Removed                                                                                                             5.1s 
 ✔ Network solidtime_internal       Removed                                                                                                             0.2s 

# docker compose up -d
WARN[0000] Found orphan containers ([solidtime-scheduler-run-37a835832e84]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. 
[+] Running 6/6
 ✔ Network solidtime_internal       Created                                                                                                             0.0s 
 ✔ Container solidtime-database-1   Started                                                                                                             1.6s 
 ✔ Container solidtime-gotenberg-1  Started                                                                                                             1.7s 
 ✔ Container solidtime-app-1        Started                                                                                                             1.8s 
 ✔ Container solidtime-queue-1      Started                                                                                                             1.9s 
 ✔ Container solidtime-scheduler-1  Started                                                                                                             1.8s 

# docker ps -a
CONTAINER ID   IMAGE                        COMMAND                  CREATED              STATUS                        PORTS                                                                             NAMES
116d43ab94c5   solidtime/solidtime:latest   "start-container"        About a minute ago   Up About a minute (healthy)   80/tcp, 443/tcp, 2019/tcp, 8000/tcp, 443/udp                                      solidtime-scheduler-1
720fc1271bc4   solidtime/solidtime:latest   "start-container"        About a minute ago   Up About a minute (healthy)   80/tcp, 443/tcp, 2019/tcp, 443/udp, 0.0.0.0:8000->8000/tcp, [::]:8000->8000/tcp   solidtime-app-1
ea155fab87b4   solidtime/solidtime:latest   "start-container"        About a minute ago   Up About a minute (healthy)   80/tcp, 443/tcp, 2019/tcp, 8000/tcp, 443/udp                                      solidtime-queue-1
89b4743a3289   gotenberg/gotenberg:8        "/usr/bin/tini -- go…"   About a minute ago   Up About a minute (healthy)   3000/tcp                                                                          solidtime-gotenberg-1
978aa7edf081   postgres:15                  "docker-entrypoint.s…"   About a minute ago   Up About a minute (healthy)   5432/tcp                                                                          solidtime-database-1
d2cccf73b84f   solidtime/solidtime:latest   "start-container php…"   9 hours ago          Exited (0) 9 hours ago                                                                                          solidtime-scheduler-run-37a835832e84

[KyletheNerd]

I can confirm this issue on Windows 11 with Docker Desktop.
The gotenberg container doesn't restart automatically after
Docker restarts because the restart policy is missing.

Adding restart: always to the gotenberg service fixed it for me.