mesh-catalog

Files

T

jochen 2fde82993d docker: read the resolver file a container really uses (hq issue 348)

On 2026-10-09 the control node's route-proxy failed every lookup against 10.10.0.1 alone for twenty
minutes while the machine's file listed both mesh resolvers; its copy lives under the runtime's
root-only directory and no tool read it. docker_resolv_conf reads /etc/resolv.conf as the container
sees it through the runtime's archive (docker cp, no exec), parses it, and says whether it lists the
same resolvers as the machine.

2026-10-09 13:33:23 +02:00

cmdline.go

Keep secrets off command lines the runtime records (hq issue 282)

2026-10-07 01:37:21 +02:00

docker_test.go

docker: say where the runtime's event history begins, so a short history never reads as a quiet one (hq issue 348)

2026-10-09 13:24:58 +02:00

docker.go

docker: say where the runtime's event history begins, so a short history never reads as a quiet one (hq issue 348)

2026-10-09 13:24:58 +02:00

main.go

docker: read the resolver file a container really uses (hq issue 348)