Deploy a Docker image

Volume usage

The Volumes screen shows the space used by each volume as reported by Docker. A driver that cannot report a size shows Unavailable, which is distinct from zero usage.

Choose the image

Any reference Docker understands works: nginx:1.27, ghcr.io/owner/app:1.4.2, registry.example.com/team/api:latest.

Public images need no credentials. Private registries work on the Free plan too: 1 stored registry credential at a time, and Pro lifts that ceiling. On both plans the login is performed on your server over the SSH connection and the credential is stored there, encrypted — it never passes through our backend.

Set ports and environment

1. 01Map the container port to a host port, or leave it unpublished if a reverse proxy will reach it over a Docker network.
2. 02Add environment variables. Values you mark as secret are encrypted on the server rather than written into the container definition in clear text.
3. 03Attach volumes if the application keeps state.
4. 04Press Deploy.

What happens on the server

MihraOps pulls the image, creates the container with the options you set, starts it and follows its state. Pull progress and container logs stream into the app while it happens.

If the image defines a health check, the container is not considered ready until Docker reports it healthy.

Publishing it on a domain

A container reachable only on a host port is fine for internal tools. To serve it on a domain with HTTPS, bind a domain to it — MihraOps configures the reverse proxy and certificates for you.