Skip to content
Kapten
Esc
↑↓navigate↵open⌘Jpreview
On this page

Deploy a container image

Run an application from an existing container image and tag, with its ports, resources and health checks.

If you already build your images, in CI or elsewhere, deploy them as they are: Kapten pulls the image and runs it.

Create the application

In your environment, create an application and choose Container as its source. Enter the image name, such as ghcr.io/acme/api, and its tag, such as 1.4.2.

Set the runtime command

Optional: override the image’s entrypoint and arguments.

Set resources and instances

Set CPU and memory requests and limits, for example a request of 250m CPU and 256Mi memory. See Resources for the units. Set the minimum and maximum number of running instances.

Declare ports and volumes

Add each port the application listens on, with its protocol, and mark one as the default. Add a persistent volume for any path whose data must survive a restart.

Add health checks

A readiness check tells Kapten when an instance can receive traffic; a liveness check restarts an instance that stopped responding. For a web service, an HTTP check on a health endpoint such as /healthz is usually enough for both.

Create and deploy

Kapten deploys the application as soon as it is created. Open it to follow the run and read its logs.

Deploy a new version

Change the application’s tag and deploy it again. To deploy several applications in a set order, use a pipeline.

Was this page helpful?