For the complete documentation index, see llms.txt.

Migration

Already using Chainguard and ready to move existing workloads over? Start with the product you’re migrating.

Migrate to Chainguard Containers

Replace the base images in your Dockerfiles with Chainguard Containers. Because Chainguard Containers are minimal — most have no shell or package manager — migration usually means adjusting how your image installs dependencies, which user it runs as, and what its entrypoint expects.

Migrate to Chainguard Libraries

Point your package manager at Chainguard Libraries and reinstall. Libraries are rebuilt from verified source as drop-in replacements, so migration is a configuration change rather than a code change.

  • Java — switch an existing Maven or Gradle project over.
  • JavaScript — switch an existing npm project over.
  • Python — switch an existing pip, uv, or Poetry project over.

Libraries are currently available for Java, Python, and JavaScript. For background on how access and configuration work, refer to the Chainguard Libraries overview.

Migrate an API integration

If you call the Chainguard API directly, v2 is Generally Available and endpoints have moved from /v1/ to /v2/.

chainctl, the Chainguard Console, and the Terraform provider handle versioning themselves, so this only applies to curl, gRPC, or custom SDK integrations.

Automate the migration

Three tools reduce the manual work, and they suit different situations:

  • Guardener Dockerfile migration — an AI agent that converts, builds, and validates your Dockerfiles until they work. Use it when a Dockerfile is complex enough that a mechanical translation won’t hold up.
  • Dockerfile Converter (dfc) — an open source tool that rewrites apt, yum, and apk instructions deterministically. Use it when you want a fast, predictable first pass you can review yourself.
  • Image Matcher — an API that reads an existing image’s SBOM and ranks the closest Chainguard equivalents. Use it when you know what you run today but not what to replace it with.

Guardener also migrates GitHub Actions to hardened, SHA-pinned equivalents and enforces signed commits. Refer to the Guardener overview for its full set of capabilities.