Skip to content

Build spec

JSON
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
{
  "apiVersion": "v1",
  "type": "build",
  "name": "myapp",
  "unit": {
    "Build": {
      "ImageTag": "localhost/myapp:latest"
    }
  },
  "containerfile": "FROM docker.io/library/nginx:latest\n",
  "contextFiles": [
    { "filename": "app.conf", "content": "file contents here", "mode": "0644" }
  ],
  "reclaimPolicy": "Retain"
}
Field Type Required Notes
apiVersion string yes "v1". See API versioning.
type string yes "build"
name string yes Referenced from a container as Image: "<name>.build".
unit object yes Quadlet sections, most importantly Build.ImageTag, which must start with localhost/<name>:. syslet rejects a build whose tag isn't local-only.
containerfile string yes The Containerfile content itself (not a path), written to the build's context directory.
contextFiles array no Build context files copied alongside the Containerfile (for COPY/ADD). Each entry: filename (relative, no path separators), content, optional mode. Not to be confused with a container's configFiles/configDirs, which bind-mount into a running container.
reclaimPolicy string no "Delete" (default) or "Retain". Controls whether the built podman image is deleted along with the unit when the build is pruned.

Build units have no removalAllowed field, and unlike containers, volumes, and networks they are pruned unconditionally once the spec disappears from the input. Only the built image is protected, by reclaimPolicy. See Removing specs.