Deploy from VideoSDK Registry

VideoSDK Cloud comes with a built-in container registry, so you can ship your agent straight from your machine. There is no external registry to set up (no ECR, GCR, ACR, or Docker Hub), and no image pull secret to manage. It is the default for the VideoSDK CLI, so you do not have to configure anything.

Prerequisites

• A working agent project with a Dockerfile.
• Docker installed and running on your machine.
• VideoSDK CLI installed and authenticated. See Installation and Authentication.

Quick Deploy

videosdk agent up builds, pushes, and deploys your agent in a single command. Use a plain image name and the CLI takes care of the rest.

videosdk agent up --image my-agent:v1

That is the full path from code to a running agent. No image pull secret required.

Step by Step

Prefer to run each stage on its own? Use build, push, and deploy.

1. Build

Build your image with a plain image name.

videosdk agent build --image my-agent:v1

2. Push

Push your image to VideoSDK Cloud. This is the default, so no extra flags are needed.

videosdk agent push --image my-agent:v1

Your image is now stored in VideoSDK Cloud, ready to deploy.

3. Deploy

Deploy the image you just pushed. No image pull secret needed.

videosdk agent deploy

To set replicas or other options, pass them as flags:

videosdk agent deploy --min-replica 1 --max-replica 3

Using Your Own Registry

Want to use your own registry instead? Pass --server with your credentials (-u/-p), or use an image name that already includes a registry host (for example, ghcr.io/me/agent:v1). See Build & Push for the full reference, and the ECR, GCR, and ACR guides for external registries.

Notes

• The image name must be lowercase.
• Docker must be installed and running.
• Images on VideoSDK Cloud do not need an image pull secret at deploy time.