Repository navigation
fix(services): start the core built-in services with the privilege lock - #1015
Open
Medformatik wants to merge 1 commit into
Open
Medformatik wants to merge 1 commit into
Medformatik wants to merge 1 commit into
Conversation
Medformatik
force-pushed
the
fix/built-in-privilege-lock
branch
from
November 16, 2026 10:00
3e0aeec to
b8e548e
Compare
Community services already ran with no-new-privileges; built-in services ran without it. The renderer now applies it to every built-in service except a listed set of engines whose start-up no automated check exercises.
Medformatik
force-pushed
the
fix/built-in-privilege-lock
branch
from
November 16, 2026 17:23
b8e548e to
15b3547
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
The Compose renderer gave community services Docker's
no-new-privilegesoption and a process limit, while built-in services ran with neither. The built-in services include the third-party engine images, and nearly all of them share one network with Redis, the data manager and the operations agent.The renderer now applies
no-new-privilegesto every built-in service by default. A named set of 21 engines keeps its previous settings for now: Nominatim, Photon, the Pelias services, Elasticsearch, MOTIS and its feed proxy, Valhalla, OSRM, OTP, BRouter, Overpass, Martin, the tile server, LocalAI and the Dawarich services. No automated check starts those images, so nothing has shown yet that they start with the lock. The rule next to the list is to remove an id once the service has been started with the lock and found healthy. A new test renders every manifest underservices/and fails when a built-in service is neither locked nor listed, or when a listed id no longer exists.The services that get the lock now are the API, the web app, the data manager, the operations agent, the Transitous runner, Traefik, the well-known file server, PostGIS and Redis. These are the nine services the install smoke test starts and checks for health, and this change triggers that test.
Not part of this change, and open for a decision: a process limit and capability drops for the engines (each needs measured values and a live run), and splitting the shared network so that an engine cannot reach Redis, PostGIS or the operations agent directly.
Related work
Ninth layer of the stack that starts with #983.
Verification
pnpm check-ops-authorityand thepackages/coretype check pass; Biome and Prettier pass on the touched files.Release and upgrade impact
Product impact: security
No operator action. The nine containers are recreated on the first
compose upafter the update.No package release: the extension CLI is counted through shared core sources, but the Compose renderer change applies to built-in services only and community rendering is unchanged.