chore: set restart: unless-stopped on every service

Coolify injects the same value when a compose service omits one, but Dokploy
runs the file as written, so in its default compose mode an omitted policy
leaves the container down after a crash or a host reboot.
This commit is contained in:
tiennm99 committed 2026-09-20 14:34:57 +07:00
1 parent b626c5b70d
commit c2b508c171
10 files changed
+29 -12

No files matched your search

+6 -2
View File
@@ -10,10 +10,14 @@ otherwise declare:
- **No published ports.** The platform attaches the container to its proxy
network and maps a domain to the internal port. Publishing one would also
expose it on the host.
- **No `restart:` policy.** The platform manages the container lifecycle.
- **No `container_name:`.** Compose derives it from the directory.
Services that do publish ports or set `restart:` say so in their own README.
Every container does set `restart: unless-stopped`. Coolify would inject the
same value on its own, but Dokploy leaves an omitted policy alone, which in its
default compose mode means the container stays down after a reboot.
Services that publish ports or set `container_name:` say so in their own
README.
## Layout