Deploy a container from an image

Use an image from Docker Hub, GHCR or your own private registry.

  1. Go to the Containers menu and click Create container.
  2. Image: pick Default Static Website, which works straight away, or My own image and enter the image name with its tag, such as ghcr.io/you/app:1.2.0. For a private registry, enter its URL (https), username and access token.
  3. Service: set the Service ID (part of the URL) and the port your app listens on (default 8080; your app gets it in the $PORT variable). Add a command and health check path if you have them.
  4. Scaling: choose the size, the minimum–maximum number of instances, and the timeout per request (up to 60 minutes).
  5. Access: open to everyone on the internet, or only inside the VPC, and choose whether an Invoker token is required.
  6. Variables: you can paste from a .env file. Tick Secret for values that should be hidden.
  7. Click Create and deploy.

Your app will open at https://name.containers.region.thailandhosting.com, as shown on the Overview page.

Set the minimum instances to 0 so the container pauses on its own when nobody is using it (after about 15 minutes), with no server charge during that time. The first request after a pause is a little slower than usual.

The Economy Machine type (chosen in the Region card) uses ARM CPUs. Your image must support linux/arm64 (build with docker buildx --platform linux/arm64).

If something goes wrong

The deploy fails and says “หา image … ใน registry ไม่พบ หรือไม่มีสิทธิ์ดึง” (Image … not found in the registry, or no permission to pull it)

Check that the image name and tag are exactly right. For a private registry, check that the token hasn’t expired and can read that package.

It says the image only has another architecture, but linux/arm64 was chosen

Rebuild the image to support arm64, or choose another machine type that isn’t ARM.

I pushed the same image tag, but the app is still the old version

The image is remembered at deploy time. Click Deploy new revision to pull the latest version.

It says “Private Registry ต้องใช้ HTTPS และ credential ที่ถูกต้อง” (A private registry needs HTTPS and valid credentials)

The registry URL must start with https://, and you must enter both the username and the token.

Still stuck? Let our team help

Open a ticket from the Console. Tell us the site or service, what you did and the message on screen. Our reply comes back in the same ticket, so everything stays in one place.

Open a ticket All guides