Skip to content

update CA FAQ #3048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SharpRake merged 4 commits into from
Mar 5, 2026
Merged

update CA FAQ #3048

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6252fc6
Add troubleshoot volume mounts for ephemeral container
timm13 Oct 2, 2025
e874ba2
Merge branch 'chainguard-dev:main' into main
timm13 Mar 5, 2026
2c67383
update CA FAQ based on a custmer ticket
timm13 Mar 5, 2026
deb7330
Update content/chainguard/chainguard-images/features/ca-docs/faq.md
SharpRake Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/chainguard/chainguard-images/features/ca-docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,12 @@ Custom Assembly provides the tools and defaults for secure image creation — bu

{{< blurb/why_ca >}}

## How do tags work for a custom assembly image (base image vs. added packages)?

For a Custom Assembly image, the semantic tag (for example, `vX.Y.Z`) always reflects the version of the Chainguard container image on which it is based. Any added packages do not get their own version tags.

When an added package is updated and available, your Custom Assembly image is rebuilt automatically and the new build that includes the updated package becomes the `latest` image. The semantic tag remains tied to the same base image digest until the base image itself is updated and a new semantic tag is created.

Comment thread
SharpRake marked this conversation as resolved.

## Custom Assembly Troubleshooting
Build failures can occur for a number of reasons, including the following:
Expand Down