Container registry
Registry (/gravity/registry) is where you find container images to
deploy and where images built from your own repositories end up.
Browsing public images
Section titled “Browsing public images”The registry opens on a curated list of well-known official images -
nginx, postgres, redis, node, python, ubuntu, and similar -
with a search box and a row of quick-search shortcuts above it. Click any
image (or a search result) to open its detail page, which shows:
- Star count, pull count, and when it was last updated.
- A tag table you can filter, each with its size and when it was pushed.
- A ready-to-copy pull command for the selected tag.
- A Deploy button that pre-fills the instance creation wizard with this image and tag.
Star the heart icon on any card to pin it to a Favourites section at the top of the default view - favourites are remembered on your device.
Your organization’s registry
Section titled “Your organization’s registry”The Sencai tab lists container packages already published to your organization’s own, private registry - the one backing your repositories. Each entry shows its type, version, and download count, with a link to view it directly. Images are published here through your organization’s Git integration as part of your CI pipeline or a manual push - see CI & pipelines for where pipeline secrets and workflow files live.
Storage in your organization’s own registry is metered against your plan:
| Plan | Private registry |
|---|---|
| Starter | 20 GB |
| Professional | 100 GB |
| Business | 1 TB |
| Enterprise | Custom |
Vulnerability (CVE) scanning is part of every plan. Findings surface in Vulnerabilities, not on this page.
Connecting an external registry
Section titled “Connecting an external registry”Custom Registries (/gravity/registry/registries, reached from the
Registry page’s own tab) connects a private Docker Registry v2 endpoint you
already run - Harbor, GitLab’s container registry, or a plain Docker
Registry v2 server - so you can browse it from inside Sencai without
switching tools.
Add registry asks for a URL, an optional username (for basic auth -
for a GitLab personal access token, set the username to oauth2), and an
optional token. Only an organization admin can add or remove a custom
registry.
Once added:
- Test connection checks reachability and reports Reachable, Unauthorized (bad or expired credentials), or Unreachable.
- Opening a connected registry lists its repositories and lets you browse tags. If the registry doesn’t expose a browsable catalog, adding an API URL (GitLab-compatible) enables discovery through that API instead; otherwise you can look up a specific repository path directly to see its tags.
- Repositories can be starred as favourites, scoped to that registry.
Editing a registry lets you update its URL, username, or token at any time - leave the token field blank to keep the existing one.
Removing images
Section titled “Removing images”Sencai doesn’t currently offer an in-app retention or bulk-cleanup policy for images in your organization’s own registry - manage lifecycle through your CI pipeline (for example, tagging conventions and pipeline-driven deletion) for now.
What’s next
Section titled “What’s next”- CI & pipelines - how images get built and pushed from your repositories
- Repositories - the Git side of the same organization namespace
- Vulnerabilities - CVE findings for scanned images
- Provision & manage instances - deploying an image from here