ocaml-docker/test/interop/dockerd/traces/ at main · gazagnaire.org/ocaml-docker · Tangled

gazagnaire.org / ocaml-docker

0

Docker Engine API types and codecs in pure OCaml

0

ocaml-docker / test / interop / dockerd / traces /

at main 5 files

Thomas Gazagnaire docker: capture errors as a typed value; add /info and conformance traces 2mo ago

docker: Engine API client and server, first slice New ocaml-docker package: the Docker Engine REST API on the host, in pure OCaml. The IO-free `docker` library maps request and response bodies to OCaml values with nox-json; `docker-client` (the `dockr` CLI) and `docker-server` (the `dockrd` daemon) are thin Eio adapters over a Unix socket, so the same definitions back the client, the server, and the tests. This first slice covers GET /version and GET /_ping (both also under a /v<api> prefix) -- enough to exercise the whole stack (Unix-socket transport, routing, headers, JSON codecs, client/server symmetry) without a container runtime behind it. The interop tests cover both directions. test/client drives a real daemon and test/interop/dockerd replays committed real-daemon captures (the oracle is contacted only at REGEN=1), validating our client against a real server. test/server points the stock `docker` CLI at our server, validating our server against a real client.

2 months ago

docker: capture errors as a typed value; add /info and conformance traces Errors: a failed request is now captured as `Docker.Error` carrying the HTTP status and the daemon's message. The client decodes the `{"message": ...}` error body instead of reporting a flat "unexpected HTTP status" string, and wraps transport failures (no daemon at the socket) as a status-0 error rather than letting the exception escape. New endpoint: GET /info, modelled as a useful scalar subset of the large info object (ignoring unmodelled members). Exposed as `Client.info` and the `dockr info` subcommand. Conformance: commit two more read-only captures from a real daemon -- the versioned path /v1.53/version (version negotiation) and a 404 error body -- and assert our codecs decode them. /info is covered by a synthetic unit test plus the live client test, not a committed trace, since the real /info carries host-specific data.

2 months ago

docker: Engine API client and server, first slice New ocaml-docker package: the Docker Engine REST API on the host, in pure OCaml. The IO-free `docker` library maps request and response bodies to OCaml values with nox-json; `docker-client` (the `dockr` CLI) and `docker-server` (the `dockrd` daemon) are thin Eio adapters over a Unix socket, so the same definitions back the client, the server, and the tests. This first slice covers GET /version and GET /_ping (both also under a /v<api> prefix) -- enough to exercise the whole stack (Unix-socket transport, routing, headers, JSON codecs, client/server symmetry) without a container runtime behind it. The interop tests cover both directions. test/client drives a real daemon and test/interop/dockerd replays committed real-daemon captures (the oracle is contacted only at REGEN=1), validating our client against a real server. test/server points the stock `docker` CLI at our server, validating our server against a real client.

2 months ago

docker: Engine API client and server, first slice New ocaml-docker package: the Docker Engine REST API on the host, in pure OCaml. The IO-free `docker` library maps request and response bodies to OCaml values with nox-json; `docker-client` (the `dockr` CLI) and `docker-server` (the `dockrd` daemon) are thin Eio adapters over a Unix socket, so the same definitions back the client, the server, and the tests. This first slice covers GET /version and GET /_ping (both also under a /v<api> prefix) -- enough to exercise the whole stack (Unix-socket transport, routing, headers, JSON codecs, client/server symmetry) without a container runtime behind it. The interop tests cover both directions. test/client drives a real daemon and test/interop/dockerd replays committed real-daemon captures (the oracle is contacted only at REGEN=1), validating our client against a real server. test/server points the stock `docker` CLI at our server, validating our server against a real client.

2 months ago

version_v153.json

docker: capture errors as a typed value; add /info and conformance traces Errors: a failed request is now captured as `Docker.Error` carrying the HTTP status and the daemon's message. The client decodes the `{"message": ...}` error body instead of reporting a flat "unexpected HTTP status" string, and wraps transport failures (no daemon at the socket) as a status-0 error rather than letting the exception escape. New endpoint: GET /info, modelled as a useful scalar subset of the large info object (ignoring unmodelled members). Exposed as `Client.info` and the `dockr info` subcommand. Conformance: commit two more read-only captures from a real daemon -- the versioned path /v1.53/version (version negotiation) and a 404 error body -- and assert our codecs decode them. /info is covered by a synthetic unit test plus the live client test, not a committed trace, since the real /info carries host-specific data.

2 months ago