Running a Docker container on 8Deploy

Docker is available on Pro and above. If your application already runs with Docker Compose, you can bring that file and run it here.

Setting it up

1. Go to Apps and choose New app.
2. Select Docker.
3. Connect the git repository containing your docker-compose.yml, or upload the compose file.
4. Tell us which service and port should receive web traffic.
5. Add your environment variables in the panel rather than committing them.
6. Choose the domain or subdomain the app should answer on.
7. Deploy.

We build and start your containers, put your chosen service behind HTTPS with a certificate we issue, and keep it running.

Persistent data

Anything written inside a container disappears when that container is rebuilt. Store anything you need to keep in a volume, or in a database created in the Databases section of your panel. Do not keep uploaded files inside the container's own filesystem.

Resources

All of your containers together run inside your account's guaranteed memory and CPU. Pro gives you 1.5 GB and 2 cores, Premium 3 GB and 4 cores, Platinum 5 GB and 6 cores. A multi-service compose file with a database, a cache and two workers will feel this. Size your plan for the total, not for one container.

If a container is stopped for exceeding memory, that is what happened. Either trim what you are running or move up a plan.

Updating

Push to the connected branch and we rebuild and restart. You can also deploy manually from the panel.

What Docker is good for

• An application with an unusual runtime we do not otherwise cover
• A stack you have already containerised and want to keep identical between your machine and production
• Self-hosted tools you want to run alongside your website

What Docker is not

It is not a way to get more resources than your plan includes. The limits are enforced at the account level, whatever you run inside them.

If you are unsure whether your compose file will work here, send it to [email protected] and we will look at it.