Authenticate to Katapult Container Registry
When using the Katapult Container Registry, you need to authenticate to access your container images.
Authentication Options
There are two ways to authenticate with Katapult Container Registry, depending on your use case:
1. Recommended: User Email & User API Token
Use this approach for most scenarios including personal development and team workflows.
- Username: Your email address (e.g.,
john@company.com
) - Password: User API token from Krystal Identity Dashboard
- Best for: When you're working on your local machine, developing applications, or need personal access to container images
2. Organization Subdomain & Organization API Token
Use this approach for automated systems and CI/CD pipelines.
- Username: Your organization subdomain (e.g.,
my-company
) - Password: Organization API token from Katapult Dashboard
- Best for: Automated deployments, CI/CD pipelines, shared infrastructure
Get an API Token
Choose the appropriate token type based on your authentication method:
For User Email Authentication
Generate a User API Token from Krystal Identity:
- Log in to your Krystal Identity account.
- Navigate to Static Access Tokens.
- Click Create new static access token.
- Give your token a name (e.g., "Container Registry Access").
- Select an expiration date for your token.
- Click Create token.
- Copy the generated token and store it securely. You will not be able to see it again.
- After copying the token, navigate to the bottom of the page and click on Manage scopes.
- Select the scopes you need:
Manage container registries
for full accessRead-only access to container registries
for read-only permissions
- Click Save scopes.
For Organization Subdomain Authentication
Generate an Organization API Token from Katapult:
- Log in to your Katapult account.
- Navigate to the API Tokens section.
- Give your token a name (e.g., "CI/CD Container Registry").
- Optional: Set Authorized IP Addresses to restrict access to your token.
- Select the scopes you need:
Core: Manage container registries
for full accessCore: Read-only access to container registries
for read-only permissions
- Click Create API token.
- Copy the generated token and store it securely. You will not be able to see it again.
Authenticate with Container Tools
Use your API token as the password when authenticating to kcr.io
. Choose the appropriate username based on your token type:
Using User Email
- Docker
- Podman
- Skopeo
- Buildah
- Helm
docker login kcr.io \
--username your-email@company.com \
--password <your-user-api-token>
podman login kcr.io \
--username your-email@company.com \
--password <your-user-api-token>
skopeo login kcr.io \
--username your-email@company.com \
--password <your-user-api-token>
buildah login kcr.io \
--username your-email@company.com \
--password <your-user-api-token>
helm registry login kcr.io \
--username your-email@company.com \
--password <your-user-api-token>
Using Organization Subdomain
- Docker
- Podman
- Skopeo
- Buildah
- Helm
docker login kcr.io \
--username <your-org-subdomain> \
--password <your-org-api-token>
podman login kcr.io \
--username <your-org-subdomain> \
--password <your-org-api-token>
skopeo login kcr.io \
--username <your-org-subdomain> \
--password <your-org-api-token>
buildah login kcr.io \
--username <your-org-subdomain> \
--password <your-org-api-token>
helm registry login kcr.io \
--username <your-org-subdomain> \
--password <your-org-api-token>