Images
Pull, inspect, tag, prune, and update Docker images, and save private registry credentials.
Pull an image
Section titled “Pull an image”- Open Images and click Pull Image.
- Enter the image reference, such as
redis:latest. If you don’t know the exact name, use Search Registry in the dialog, then pick a result and a tag. - Click Pull. The image appears once the download finishes.
Browse images
Section titled “Browse images”Open Images in the sidebar. The table shows each image’s tag, ID, size, and creation date. If you have scan results, sort Vulnerabilities to order by vulnerability count.
Inspect an image
Section titled “Inspect an image”Click the image’s name, ID, or Inspect. The detail page shows tags, configuration, layer history, vulnerability results, and labels.
- History tab: layer IDs, creation time, size, command, tags, and comments. Use it to see how an image was built, or to compare images after a rebuild.
- Attestations tab: in-toto attestations, which are signed statements published with an image, such as build provenance or an SBOM. Filter by platform and predicate type. Open one for its digest, media type, statement type, subject, platform, and size.
Attestations need a registry tag or digest Arcane can resolve, so local-only images may have none.
Tag an image
Section titled “Tag an image”- On the image detail page, click Tag Image. This needs
images:tag. - Enter the target repository and tag. Without a tag, Docker uses
latest. - Click Save.
Remove an image
Section titled “Remove an image”- Click the trash icon on the image row.
- Confirm.
Images used by any container can’t be removed.
Prune unused images
Section titled “Prune unused images”- Click Prune Unused.
- Pick Dangling Only (images without tags) or All Unused (every image no container uses).
- Confirm.
Check for image updates
Section titled “Check for image updates”- Click Check Updates. This asks registries for newer images. Refresh only reloads the list.
- Open an image’s update indicator. It shows the running and the latest version or digest, each with its build date.
- Optional: click Release notes to read the GitHub release for the new version.
- Update the containers using the image, or select Re-check Updates.
An image’s detail page shows the same update status. Its Pull action pulls the image’s tag again, which needs images:pull.
Arcane also checks on the Auto Updates schedule. Updated images show one of:
- Version Update: a newer version tag is available.
- Digest Update: the same tag now points to a different build. Its digest (the registry’s content hash for one exact image) changed. Common with tags like
latest.
If updates don’t appear, check that Arcane can reach the registry and has its credentials.
Release notes
Section titled “Release notes”Arcane finds release notes through the image’s org.opencontainers.image.source label (or its url or documentation label).
- A GitHub source opens the matching GitHub release in a dialog.
- A non-GitHub source shows a link to the project page.
- An image with none of these labels has no release notes.
Unauthenticated GitHub requests are limited to 60 per hour. To raise that to 5,000, set GitHub Token under Settings → Automations.
Docker Hardened Images
Section titled “Docker Hardened Images”Arcane reads the com.docker.dhi.* labels on Docker Hardened Images. Its badge on the image, and on containers that use it, shows the support status:
- Hardened: supported.
- Ending soon: support ends within 30 days. Rebuild on a newer version.
- End of life: support has ended.
The image’s Docker Hardened Image tab lists its version, distribution, variant, compliance, release and end-of-life dates, shell, and package manager, with View in catalog.
- Filter the Images table by Docker Hardened Image: Hardened, Ending soon, End of life, or Not hardened.
- The Dashboard flags agents with hardened images past or near end of life.
Private registries
Section titled “Private registries”Save registry credentials so Arcane can pull private images and check them for updates.
- Open Images → Registries.
- Add the registry host, username, and password or token.
- Optional: add Repository Names.
- Click Save.
You can save several registries. Arcane picks credentials by matching the hostname in each image reference.
Repository names
Section titled “Repository names”List the repositories you push to on this registry, one complete name per line:
team/apiteam/platform/api- Arcane validates each name against Docker’s reference format and removes duplicates.
- They fill the Repository name dropdown when pushing builds.
- Without them, a registry works for pulls and update checks, but can’t be a push target.
Browse a registry
Section titled “Browse a registry”- On a saved registry, click Browse. This needs
registries:readandregistries:browse. - Pick a repository to see its tags, each with digest, size, platforms, and a copyable image reference.
- Optional: delete tags one at a time or in bulk. This needs
registries:delete-tags.
Which repositories show up:
- Catalog registries, such as self-hosted Distribution, list every repository.
- Docker Hub, GHCR, and similar don’t, so Arcane shows the saved Repository Names.
- To load any other repository, type it into Open Repository.
Amazon ECR
Section titled “Amazon ECR”ECR is a first-class registry type. Enter an AWS access key ID, secret access key, and region. Arcane exchanges them for a temporary ECR token and refreshes it as needed.
When you change an ECR registry’s URL, re-enter both the access key ID and the secret access key.