> ## Documentation Index > Fetch the complete documentation index at: https://docs.levelrail.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy a Docker app to your own server > Deploy a Docker image to your own Linux server with Levelrail, attach a custom domain, ship a second version, and roll back in one command. About 10 minutes. By the end of this tutorial you will have a Docker image running on your own server, reachable on a domain you control, with a second version deployed and a one-command rollback to the first. It takes about ten minutes and needs no Dockerfile or build step. ## Before you start * A running Levelrail instance. If you do not have one, [install it](/installing) first. * The CLI, logged in to that instance: see [Installing just the CLI](/installing#installing-just-the-cli). * Optional: a domain whose DNS you can edit. The examples deploy the public `nginx` image so you can follow along without any code of your own. Swap in any image you like. ```bash theme={"dark"} levelrail-cli apps create --name hello --image nginx:alpine --port 80 ``` ```text theme={"dark"} app "hello" created name: hello image: nginx:alpine@sha256:df221db836e1... port: 80 ``` Levelrail resolves the tag to a digest and pins it, so what you deployed is exactly what keeps running. Block until the app is up: ```bash theme={"dark"} levelrail-cli apps wait hello ``` ```text theme={"dark"} waiting for "hello" to converge... (pending) waiting for "hello" to converge... (succeeded) "hello" rolled out ``` The exit code tells a script whether it worked: `0` for success, non-zero for a failed or timed-out rollout. ```bash theme={"dark"} levelrail-cli apps status hello ``` ```text theme={"dark"} TYPE STATUS REASON MESSAGE LAST TRANSITION EgressPolicyReady Unknown NotConfigured 2026-10-05T02:15:40Z Ready True AlreadyRunning 2026-10-05T02:15:40Z ``` `Ready: True` is the line that matters. Every reconcile records a condition with a reason, so a failure always comes with an explanation instead of a blank status. ```bash theme={"dark"} levelrail-cli apps domains add hello hello.example.com ``` Then create an `A` record for that name pointing at your server's public IP. Check whether DNS has caught up: ```bash theme={"dark"} levelrail-cli domains check hello hello.example.com ``` ```text theme={"dark"} domain: hello.example.com status: not_resolving expected: 203.0.113.10 ``` `not_resolving` means the record has not propagated yet. Run the check again in a few minutes. Routing starts as soon as the domain is added, with no proxy to configure: Levelrail embeds Caddy and updates its routes itself. ### What about HTTPS? Every routed domain gets a TLS certificate automatically. Out of the box it is self-signed, so browsers show a trust warning. That is fine for internal tools and first trials. Real Let's Encrypt certificates are switched on under **Settings, Domains**: enter an account email and enable ACME, with ports 80 and 443 open to the internet. See [Domains and ingress](/domains-and-ingress#real-public-acme-let-s-encrypt-or-rfc-8555-ca) and the [ACME verification runbook](/acme-verification-runbook) if issuance fails. If you have no domain at all, a hostname of the form `.sslip.io` works with no DNS record; see [Zero DNS setup](/domains-and-ingress#zero-dns-setup-sslip-io-hostnames-and-one-click-https). ```bash theme={"dark"} levelrail-cli apps deploy hello --image nginx:1.27-alpine levelrail-cli apps wait hello ``` Every deploy is recorded. List the history: ```bash theme={"dark"} levelrail-cli apps deploys list hello ``` ```text theme={"dark"} ID IMAGE DIGEST SOURCE STATUS ROLLOUT STARTED dep_IUrA3qUFg7DV nginx:1.27-alpine 65645c7bb6a0 image succeeded serving 2026-10-05T02:15:47Z dep_FnrJJJnuh0Md nginx:alpine df221db836e1 image succeeded serving 2026-10-05T02:15:38Z ``` The Deployments page listing every deploy across apps, with status and rollback actions The same history is on the dashboard's **Deployments** page, across every app. Something wrong with version two? Roll back to the first deploy by its ID: ```bash theme={"dark"} levelrail-cli apps deploys rollback-to hello dep_FnrJJJnuh0Md levelrail-cli apps wait hello ``` ```text theme={"dark"} app "hello" now targets image "nginx:alpine@sha256:df221db836e1..." ``` No rebuild happens. Levelrail keeps previous images pinned, so garbage collection cannot remove a rollback target, and the rollback is just another deploy of an image it already has. To roll back to a specific image tag instead of a past deploy, use `levelrail-cli apps rollback hello --image nginx:alpine`. The `--image` flag is required there. ## Clean up ```bash theme={"dark"} levelrail-cli apps delete hello ``` ## Where to go next * [Zero-downtime deploys with health checks](/tutorials/zero-downtime-deploys-with-health-checks): make a bad release fail before it takes over. * [Deploy from GitHub Actions](/tutorials/deploy-from-github-actions): run this same flow on every push. * [Deploy safety](/deploy-safety): the guarantees behind pinned images and rollback. * [Deploying apps](/deploying-apps): git builds, Compose, and `app.yaml` as other ways to create an app. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.