Bundle MsQuic in server runtime image
Foundation / checks (deploy) (push) Successful in 2m51s
Foundation / checks (ecs) (push) Successful in 1m52s
Foundation / checks (client) (push) Successful in 12m46s
Foundation / checks (network) (push) Successful in 9m44s
Foundation / checks (tsan) (push) Successful in 7m51s
Foundation / checks (checks) (push) Successful in 31m29s
Foundation / checks (postgres) (push) Successful in 39m28s
Foundation / postgres-tools (push) Successful in 10s
Foundation / image (push) Successful in 2m17s
Foundation / server-image (push) Successful in 3m20s

This commit is contained in:
dingo
2026-10-04 19:13:10 -04:00
parent 11e13d7c58
commit 432bae6e2a
3 changed files with 14 additions and 8 deletions
+4 -3
View File
@@ -49,9 +49,10 @@ each from a fixed enum. There are no world, region, entity or request labels:
the scrape target carries region identity. The exposition is about 3.5 KB and at
most 8 KiB. Commit lag saturates at zero rather than wrapping.
**Image** (`server-runtime` Docker target) contains `evo-server` and the pinned
libpq, and installs only the runtime libraries it needs (libstdc++, libssl3,
zlib, CA certificates):
**Image** (`server-runtime` Docker target) contains `evo-server`,
`evo-world-clone`, the pinned libpq, and the matching pinned MsQuic shared library
when built with the QUIC listener enabled. It installs only the runtime libraries
it needs (libstdc++, libssl3, zlib, CA certificates):
- It runs as UID/GID 10001 with a read-only root filesystem and all capabilities
dropped. It exposes port 9100 and has no default configuration.
- With missing settings it exits 2 with usage; there is no default region,