Skip to main content

Module actions

Module actions 

Source
Expand description

Docker Engine API actions.

One event, eight actions. Each read the model answers has exactly one action that answers it (resource in the event says which), plus send_docker_error for a refusal in Docker’s own {"message": …} shape. Every action carries structured fields; NetGet renders the JSON document the Docker CLI’s Go decoder expects, filling what the model left out.

Structs§

DockerProtocol
Docker Engine API protocol handler.

Statics§

DOCKER_API_REQUEST_EVENT
Any read the model decides: version, info, container list/inspect, images, networks, volumes.

Functions§

event_for_resource
The event to raise for a request whose route resolved to resource: the route’s own narrowed docker_api_request, or the declared one with every action for anything else.
example_static_actions
One answer per route. A static handler answers every docker_api_request with the same action list, and the server picks the action that answers the route the request hit, so a fixed host is one static rule.