The agent file as an OCI artifact
Top: docker-agent share push sends fixtures/agents/files.yaml to the local registry localhost:15000 as m101/agent:v1. share pull writes an identical copy named localhost:15000_m101_agent:v1.yaml into the current directory, and docker-agent run with the reference answers README.md has 1 line. Bottom: the manifest the registry serves. Its mediaType is the OCI image manifest, its artifactType is application/vnd.docker.agent.config.v1+json, and the config and the one layer keep Docker image media types. Four annotations: io.docker.agent.version and io.docker.cagent.version, both v1.149.0, and the OCI created and description keys. With --key, the proof is recorded as more annotations, which this capture did not do.
files.yaml
agent root
filesystem, shell
localhost:15000
m101/agent:v1
plain HTTP
registry:2
share pull
identical YAML
in the current dir
run by reference
README.md has 1 line.
share push
share pull
run
manifest of m101/agent:v1, as the registry serves it
mediaType
application/vnd.oci.image.manifest.v1+json
artifactType
application/vnd.docker.agent.config.v1+json
config
application/vnd.docker.container.image.v1+json
layers[0]
application/vnd.docker.image.rootfs.diff.tar.gzip
annotations
io.docker.agent.version
v1.149.0
io.docker.cagent.version
v1.149.0, the legacy key
org.opencontainers.image.created
<ts>
org.opencontainers.image.description
OCI artifact containing files.yaml
with --key: a signature or MAC is added as annotations, not in this capture