Container Registry
IBEE Container Registry is a private place to store the container images your apps run — the packages you build with docker build. You push an image once, and your VMs, Kubernetes clusters and CI pipelines pull it from registry.ibee.ai. Every image you push is scanned for known security problems automatically.
Images are named like this:
Docker, Podman, containerd, Kubernetes and CI systems all work with it, because it follows the standard OCI (Open Container Initiative) image format.
Container Registry is turned on per organization. If Container Registry isn’t in your sidebar under Infrastructure, contact support to request access.
When to use Container Registry
How it works
- Create a registry in a workspace and choose a storage plan (a fixed monthly storage quota).
- Create an access token — a username and password for Docker, limited to chosen registries.
docker login,docker push,docker pullagainstregistry.ibee.ai. Each push is scanned.
Before you begin
- Billing set up for your organization: each registry has a paid storage plan, and Billing must approve it. See Add billing.
- A workspace to hold the registry, and permission to create resources in it.
- Docker (or another OCI client) on the machine that pushes or pulls.
Create a registry
Open Container Registry
Select your organization and workspace, click Container Registry under Infrastructure, then click Create registry.
Name the registry
Enter a Registry name. The portal checks it as you type and shows Registry name is available. when it’s free.
- 3–48 characters: lowercase letters, numbers and hyphens.
- Start with a letter; end with a letter or number.
- Unique across all of IBEE, and it can’t be changed later. A deleted registry’s name is never reused.
- Reserved names are refused, including
admin,docker,harbor,ibee,library,private,public,registry,support,systemand any name starting withibee-.
Choose visibility
For Public, tick I understand that anyone can pull images from this public registry, and I acknowledge the public download charges. Pushing always needs a token with push permission.
If Billing doesn’t approve the plan, a Billing needs attention dialog explains why — for example An initial wallet top-up is required before you can create or upgrade a container registry. Add funds under Billing and try again.
Create an access token
Docker logs in with a registry access token, not your IBEE password or a platform API token.
The access token is shown once and can’t be recovered. If you lose it, rotate the token to get a new one.
Log in, push and pull
The username contains a $ character, so wrap it in single quotes on the command line:
Docker prints Login Succeeded. In CI, pass the token on standard input so it never appears in logs:
Build and push an image, or tag and push one you already have:
Pull by tag, or by digest (the image’s fixed sha256: fingerprint) when you need exactly the same image every time:
The Overview tab’s Docker instructions section shows these commands with your registry filled in.
Pull from Kubernetes
Create an image pull secret from a Pull only token and reference it in your workloads:
Verify
docker pullof the image you pushed succeeds from another machine.- On the registry’s Overview tab, the repository is listed with its artifact count, pull count and last update. Open it to see one row per image digest, with tags shown on the digest they point to.
https://registry.ibee.ai/v2/answers401 Unauthorizedto a browser. That’s expected: it means the registry is reachable and needs a login.
Review image security
Open the registry’s Security tab. Scanning runs automatically on every push.
- Vulnerabilities: known security problems (CVEs — public IDs for vulnerabilities such as
CVE-2024-3094) in the packages inside your images, counted by severity. Filter by CVE or advisory ID, Severity, Repository, Image tag or digest or Package. Each finding shows the installed and fixed versions and a CVSS score (0–10 severity). Click Rescan to scan an image again; old results stay visible until the new scan finishes. - SBOMs: a software bill of materials, the list of every package in an image, in SPDX or CycloneDX format. Click Components to search it by name, version, license or supplier.
Storage, quota and clean-up
Your storage plan is a hard limit. When a push would take the registry over its quota, the push is refused; pushes work again after you delete images or upgrade the plan.
Deleting is how you free space:
- Pushing a new image to an existing tag moves the tag. The previous image stays in the repository as an untagged digest and still uses storage until you delete it.
- Delete images and repositories with the API:
DELETE /container-registry/registries/{registry_id}/artifacts/{reference}?workspace_id=…orDELETE …/repositories/{repository_name}?confirm=true&workspace_id=…. The portal has no delete for these, and the API is temporarily paused. If you need to free space before it resumes, contact support.
Check usage on the Metrics tab: storage used, storage quota, quota utilization, and outbound bandwidth over 24 hours, 7 days or 30 days.
Upgrade the storage plan
On the Settings tab, choose a larger plan under Upgrade storage plan and click Upgrade plan. The tab shows Upgrade in progress while it’s applied. Plans can only be upgraded, not downgraded.
Change visibility
On the Settings tab, choose Private or Public and click Make Private or Make Public. Making a registry public requires the same acknowledgement as at creation.
Rotate or revoke a token
The Registry access tokens tab lists each token with its registry, permission, creation date and status (Active, Expired or Revoked).
- Rotate issues a new access token and stops the old one immediately. Update every place that uses it.
- Revoke stops the token immediately. Workloads using it can no longer pull or push.
Delete a registry
Deleting a registry permanently removes its repositories, images, tags and the access tokens scoped to it. The name can never be used again.
Empty the registry
A registry must be empty before it can be deleted. Delete its repositories with the API (see Storage, quota and clean-up). While the API is paused, contact support if you need to empty a registry.
Billing
- Storage is billed monthly for the plan you chose, whatever you actually use.
- Outbound bandwidth (image pulls) is billed per GB. Private and public registries have separate rates, shown on the create page and the Settings tab. Anonymous pulls from a public registry are billed to you.
Use the API
Temporarily paused: managing Object Storage and Container Registry through the API, SDKs, CLI and Terraform. Until it resumes, these calls answer 404 with an empty body. That doesn’t mean your resource was deleted. The portal, S3 file traffic, registry pushes and pulls, and your existing resources keep working. The API, CLI and Terraform steps for these products apply once it resumes. If you use Terraform, read this first.
The API manages registries, tokens, repositories, images, scans and metrics. All paths start with https://api.ibee.ai/v1/container-registry, need the workspace_id query parameter, and a platform API token with container-registry.read or container-registry.write. Pushes and pulls still go through registry.ibee.ai with an access token.
Create and upgrade take the plan’s SKU (stock-keeping unit, the plan’s catalog code) in billing_catalog.sku_code. Create can return 202 while provisioning continues: poll until observed_state is ACTIVE. Lists are paged with page and page_size (at most 100). Token secrets are returned once, by create and rotate.
Limits
Troubleshooting
Related pages
- API Tokens
- Cloud VMs
- Secret Manager: store registry tokens for deploy pipelines
- Object Storage
