Skip to content

Containers

A container is a single standalone image published on a port. It is similar to a service but simpler. It has no manifest or nginx front. You reach it at <slug>.althostproxy.com through the HTTP proxy.

Creating

Create it from the portal (Containers → New) or the API:

POST /v1/containers
{ "name": "cache-ui", "image": "nginx:alpine", "port": 80, "memory": 256, "nodeId": "<computer>" }

The runner pulls the image and runs it as althost-ct-<id>. It publishes the container port on a host port. The tunnel proxies to that host port. Status syncs to active once the container runs. Logs stream to the control plane. They appear on the container's page.

Clients can open WebSocket connections to a container through the proxy. The proxy relays the upgrade over the tunnel. See Architecture.

Lifecycle

  • Delete sets the container to deleting. The runner stops and removes it on its next reconcile.
  • The runner captures container output the same way as services. You can read it at GET /v1/containers/:id/logs.