Customizable stop wait time

Configurable via a global `stop_wait_time` option.
The default is `10` which matches Docker defaults.
This commit is contained in:
Jacopo
2023-03-24 14:57:49 +01:00
parent 1f196045a9
commit 9b43a6b23b
4 changed files with 16 additions and 4 deletions

View File

@@ -333,6 +333,15 @@ servers:
That'll start the job containers with `docker run ... --cap-add --cpu-count 4 ...`.
### Using a different stop wait time
On a new deploy, each old running container is gracefully shut down with a `SIGTERM`, and after a grace period of `10` seconds a `SIGKILL` is sent.
You can configure this value via the `stop_wait_time` option:
```yaml
stop_wait_time: 30
```
### Using remote builder for native multi-arch
If you're developing on ARM64 (like Apple Silicon), but you want to deploy on AMD64 (x86 64-bit), you can use multi-architecture images. By default, MRSK will setup a local buildx configuration that does this through QEMU emulation. But this can be quite slow, especially on the first build.