Skip to main content

Quickstart

Deploy a first container on SailOps, expose it through HTTPS, and verify that it is reachable from the internet.

This page focuses on the shortest production-like path: one project, one container, one gateway, one route, and one DNS record.

Prerequisites​

Before you start, make sure you have:

  • A SailOps account
  • A project in your organization
  • A Docker image to deploy, such as nginx:latest for a first test
  • A domain name you control, such as app.example.com

1. Open Your Project​

  1. Sign in to SailOps.
  2. Select your organization.
  3. Open the project where you want to deploy the application.

If you do not have a project yet, create one from the project selector before continuing.

2. Create the Container​

  1. In the project sidebar, open Containers.
  2. Click Create Container.
  3. Fill in the minimum configuration:
FieldValue
Namequickstart-app
Imagenginx:latest
Port80
Compute classEco for a first test
  1. Click Create. The container is created in Stopped state.
  2. Open quickstart-app from the container list, click Start, and confirm.
  3. Wait until the container is healthy: the current console shows Running, with all instances ready. Then continue with the gateway and route.

3. Create a Gateway​

Gateways receive public HTTP and HTTPS traffic for your project.

  1. Open Gateways.
  2. Click Create Gateway.
  3. Configure the gateway:
FieldValue
Namequickstart-gateway
Gateway classgw-small
  1. Add an HTTPS listener for your hostname:
FieldValue
Namehttps
ProtocolHTTPS
Hostnameapp.example.com
Port443
  1. Click Create Gateway.
Custom domain required

SailOps does not issue default application subdomains for custom gateway traffic. Use a domain you control and point it to the gateway address.

4. Configure DNS​

After the gateway is created, open its details and copy the public address shown by SailOps.

Create or update the DNS record for your hostname:

Type: A
Name: app
Value: <gateway-address>

DNS propagation and TLS certificate provisioning can take a few minutes.

5. Add a Route​

Routes connect incoming gateway traffic to a workload in your project.

  1. Open the gateway.
  2. Go to Routes.
  3. Click Add Route.
  4. Configure the route:
FieldValue
Hostnameapp.example.com
Path/
Targetquickstart-app
Port80
  1. Save the route.

6. Verify the Deployment​

Open your hostname in a browser:

https://app.example.com

If the page does not load immediately, wait for DNS and certificate provisioning to finish, then retry.

Next Steps​

After the first deployment, continue with the guides that match your application:

Troubleshooting​

The Container Is Not Healthy​

If the status is Stopped, click Start and confirm. Otherwise, open the container details and check Events and Logs. Common causes include an invalid image name, a private image without registry credentials, or an application listening on a different port.

The Hostname Does Not Resolve​

Verify that the DNS record points to the gateway address shown in SailOps. DNS changes can take time depending on your provider and TTL.

HTTPS Is Not Ready​

SailOps provisions certificates automatically after the gateway listener and DNS are valid. Check the gateway status if HTTPS remains unavailable.