App Store template
registry icon

registry

registry is an implementation of the OCI Distribution Specification. gui-registry is a web UI for registry.

Launch in your Sealos workspace.

registry template preview
Template previewFull screenshot
Template deployments
13 on Sealos
Deployment
Your own instance
Category
Tools

About this template

Overview

The registry is an implementation of the OCI Distribution Specification, providing a standards-based solution for storing and distributing container images.

From the documentation

The gui-registry is a web UI for managing the registry, offering a user-friendly interface for common tasks such as pushing, pulling, and managing images.

How to deploy registry

  1. Choose Deploy now to start registry in your Sealos workspace.
  2. Sign in to Sealos and review the template configuration in your workspace.
  3. Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the registry template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.

Template configuration and setup

Access after deployment

Use the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.

Hosting and billing

Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.

Compare Sealos resource plans
Read full documentationCollapse documentation

For current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.

OCI Distribution Specification Registry and GUI-Registry

Overview

The registry is an implementation of the OCI Distribution Specification, providing a standards-based solution for storing and distributing container images.

The gui-registry is a web UI for managing the registry, offering a user-friendly interface for common tasks such as pushing, pulling, and managing images.

Default Credentials
  • Username: root
  • Password: root

Example Configuration

External Network Addresses
Pushing an Image to the Registry
  1. Login to the Registry:

    docker login registry.cloud.sealos.io
    
    • Username: root
    • Password: root
  2. Tag the Image:

    docker tag nginx:latest registry.cloud.sealos.io/nginx:latest
    
  3. Push the Image:

    docker push registry.cloud.sealos.io/nginx:latest
    
  4. Change the root password: Edit the registry_htpasswd file in applaunchpad's registry app to change the root password using Bcrypt.

    Note: you can ues https://httpd.apache.org/docs/2.4/programs/htpasswd.html to generate the htpasswd file.

  5. Config the registry See: https://distribution.github.io/distribution/about/configuration for more configuration

Web Management

This setup allows you to manage your container images easily through both command-line operations and a graphical web interface. Make sure to replace the default credentials with more secure options in a production environment.

From launch to everyday operations

Why deploy
on Sealos

A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.

  1. One-click deployment

    Start with a ready-made template. Review its configuration and launch from the Sealos console.

  2. Managed Kubernetes

    Run on managed infrastructure with built-in workload scheduling and recovery.

  3. Automatic HTTPS

    Give your application a public HTTPS endpoint with certificates managed for you.

  4. Persistent storage

    Keep application data on persistent volumes across container restarts.

  5. Room to grow

    Adjust CPU, memory, and replicas from the console as your workload changes.

One template. Connected resources.

You Get the Whole Stack

Sealos provisions the resources defined by your template and brings them together in your workspace.

  • App Service

    Container workloads with configurable CPU, memory, and replicas.

  • Public HTTPS URL

    An address for your app, with managed TLS certificates.

  • Database

    A database provisioned alongside your app when the template calls for one.

  • Persistent Volume

    Storage for the files and data your application needs to keep.

  • Environment Variables

    Application settings and secrets configured in one place.

  • Logs & Metrics

    Inspect container logs and resource usage from the console.

Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.

Explore more production-ready templates.

More