Skip to content

fix(services): start the core built-in services with the privilege lock - #1015

Open
Medformatik wants to merge 1 commit into
fix/privacy-export-admissionfrom
fix/built-in-privilege-lock
Open

Medformatik wants to merge 1 commit into
fix/privacy-export-admissionfrom
fix/built-in-privilege-lock

Conversation

@Medformatik

@Medformatik Medformatik commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

What changed and why

The Compose renderer gave community services Docker's no-new-privileges option 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-privileges to 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 under services/ 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

  • Focused tests pass (191 tests in eleven files), including the new all-manifests test and the Compose renderer, containment and host-authority tests. The new test fails when a locked service is unlocked without being listed and when a listed id does not exist.
  • pnpm check-ops-authority and the packages/core type check pass; Biome and Prettier pass on the touched files.
  • Not done locally: starting any container with the lock. The install smoke test on this pull request is the live check for the nine services.

Release and upgrade impact

Product impact: security

No operator action. The nine containers are recreated on the first compose up after 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.

@Medformatik Medformatik self-assigned this Nov 16, 2026
@Medformatik
Medformatik added this pull request to stack #985 November 16, 2026 09:57
@Medformatik
Medformatik force-pushed the fix/built-in-privilege-lock branch from 3e0aeec to b8e548e Compare November 16, 2026 10:00
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
Medformatik force-pushed the fix/built-in-privilege-lock branch from b8e548e to 15b3547 Compare November 16, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant