Changes for version 0.002 - 2026-05-17
- HTTP role: `_request` now accepts a `headers => {}` option to set extra HTTP request headers. Headers are sanitised against CR/LF injection. Used by `images->push` to send `X-Registry-Auth`, and available to any caller that needs custom headers.
- `images->push` now always sends an `X-Registry-Auth` header — the Docker Engine refuses pushes without it (`HTTP 400: missing X-Registry-Auth: invalid X-Registry-Auth header: EOF`). A new `auth` option accepts a hashref of credentials (`username`, `password`, `serveraddress`, or `identitytoken`) which is JSON-encoded and base64url-wrapped per the Docker Engine spec. Without `auth` the header carries an empty JSON object so unauthenticated/public pushes succeed where they previously failed at the HTTP layer.
Modules
Perl client for the Docker Engine API
Docker Engine Containers API
Docker Engine Exec API
Docker Engine Images API
Docker Engine Networks API
Docker Engine System API
Docker Engine Volumes API
Docker container entity
Docker image entity
Docker network entity
HTTP transport role for Docker Engine API
Docker volume entity