How to run a Node.js, Python or .NET app as a container
Create a container from a preset or any image, get a subdomain and certificate, and learn which port the app must listen on.
Websites, Containers runs an application as a rootless Podman container owned by your account, with its own subdomain and certificate. It needs a License to create new ones.
Steps
- Choose a preset (ASP.NET Core, Node.js, Python, Ruby or Java) or name an image. A preset pre-fills the official image, the port and the volume.
- Pick a subdomain for the container. It must not belong to another client's names.
- Read the page's hint: it tells you where to put your code and which port to listen on. Apps must listen on
0.0.0.0, not only on localhost, or the proxy cannot reach them. - Create it. The container gets a loopback-only port from 33000 upward; visitors reach it through your subdomain on 443.
- Upload your code to the volume and restart if needed.
What to know
- Containers count against your plan and your disk quota, stop when the account is suspended, and come back after a node reboot.
- A Kubernetes manifest can be deployed through the API (
POST /api/contenedores/kube); host ports, host networking and privileged containers are rejected. There is no screen for this yet. - If the license lapses, existing containers keep running; creating new ones is blocked and removing is never blocked.
Last updated: 2026-10-10