The last item was the socket inside a build sandbox for Werkator's own
integration tests. It is in place: a systemd user unit serves a werkdock
API socket in Werkator's build-environment home, .werkator.yml points
DOCKER_HOST at it, and the Testcontainers smoke test that had skipped
itself on every host that mattered now runs on the webspace and passes.
That test is this RFC's alarm. If werkdock's Engine API subset ever
stops being enough for Testcontainers, Werkator's own build says so
rather than a person noticing months later.
The last item was the socket inside a build sandbox for Werkator's own
integration tests. It is in place: a systemd user unit serves a werkdock
API socket in Werkator's build-environment home, .werkator.yml points
DOCKER_HOST at it, and the Testcontainers smoke test that had skipped
itself on every host that mattered now runs on the webspace and passes.
That test is this RFC's alarm. If werkdock's Engine API subset ever
stops being enough for Testcontainers, Werkator's own build says so
rather than a person noticing months later.
Documentation only, no version bump.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The last item was the socket inside a build sandbox for Werkator's own
integration tests. It is in place: a systemd user unit serves a werkdock
API socket in Werkator's build-environment home, .werkator.yml points
DOCKER_HOST at it, and the Testcontainers smoke test that had skipped
itself on every host that mattered now runs on the webspace and passes.
That test is this RFC's alarm. If werkdock's Engine API subset ever
stops being enough for Testcontainers, Werkator's own build says so
rather than a person noticing months later.
Documentation only, no version bump.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mi
manually merged commit aa5ea091ae into main2026-09-11 10:20:10 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The last item was the socket inside a build sandbox for Werkator's own
integration tests. It is in place: a systemd user unit serves a werkdock
API socket in Werkator's build-environment home, .werkator.yml points
DOCKER_HOST at it, and the Testcontainers smoke test that had skipped
itself on every host that mattered now runs on the webspace and passes.
That test is this RFC's alarm. If werkdock's Engine API subset ever
stops being enough for Testcontainers, Werkator's own build says so
rather than a person noticing months later.
Documentation only, no version bump.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com