With the slirp4netns port driver a rootless daemon publishes ports on
its child address only, not on localhost. Werkator now asks rootlesskit
(GET /v1/info on dockerd-rootless/api.sock) before every Docker build
and passes that address as TESTCONTAINERS_HOST_OVERRIDE, in both network
modes; the builtin driver keeps the defaults. A daemon switched between
drivers needs no configuration change. docker.env still wins.
With the slirp4netns port driver a rootless daemon publishes ports on
its child address only, not on localhost. Werkator now asks rootlesskit
(GET /v1/info on dockerd-rootless/api.sock) before every Docker build
and passes that address as TESTCONTAINERS_HOST_OVERRIDE, in both network
modes; the builtin driver keeps the defaults. A daemon switched between
drivers needs no configuration change. docker.env still wins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the slirp4netns port driver a rootless daemon publishes ports on
its child address only, not on localhost. Werkator now asks rootlesskit
(GET /v1/info on dockerd-rootless/api.sock) before every Docker build
and passes that address as TESTCONTAINERS_HOST_OVERRIDE, in both network
modes; the builtin driver keeps the defaults. A daemon switched between
drivers needs no configuration change. docker.env still wins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
With the slirp4netns port driver a rootless daemon publishes ports on
its child address only, not on localhost. Werkator now asks rootlesskit
(GET /v1/info on dockerd-rootless/api.sock) before every Docker build
and passes that address as TESTCONTAINERS_HOST_OVERRIDE, in both network
modes; the builtin driver keeps the defaults. A daemon switched between
drivers needs no configuration change. docker.env still wins.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com