Deploy pre-built container images from Docker Hub, GitHub Container Registry, or other container registries to your environments.

​
Prerequisites

Before you begin, ensure you have:

​
Connect Private Registry

1

Choose Registry

We support the following container registries:

  • Docker Hub (default)
  • GitHub Container Registry
  • Google Container Registry
  • Amazon Elastic Container Registry
  • Azure Container Registry
2

Add Registry Credentials

For private registries, add your credentials through Settings in the Ryvn Dashboard.

​
Create Your Service

1

Open Dashboard

Open the Ryvn Dashboard and go to the Services tab

2

Start Creation

Click Create Service in the top-right corner
3

Choose Service Type

Select your service type:

TypeDescription
ServerLong-running service that handles HTTP/HTTPS traffic
WorkerLong-running service for background processing
JobShort-lived task that runs to completion
4

Select Registry

Choose Container Registry and select your registry from the dropdown
5

Select Image

Select your image from the dropdown
6

Create

Click Create

​
Deploy to Environment

1

Navigate to Environment

Go to the Environments tab in the Ryvn Dashboard and select the environment where you want to deploy your container.

2

Start Installation

Click Add Service and select your container service from the list.
3

Configure Installation

Review and adjust your installation settings: - Resource allocation - Port configuration (if deploying a server) - Environment variables

4

Deploy

Click Create Installation. Ryvn will begin pulling your container and creating the necessary resources in your environment.

Once deployed, you can monitor your installation’s status directly from the dashboard. View container status, check resource utilization, and access logs to ensure everything is running as expected.

​
Release Management

Ryvn integrates with your existing release workflow:

​
Troubleshooting

​
Container Requirements

Your container image should:

  • Use semantic versioning for tags (e.g., 1.2.3)
  • Define a valid ENTRYPOINT or CMD
  • Handle process signals properly for graceful shutdowns
latest tags are not allowed as they make versioning and rollbacks unpredictable.