Skip to content
Odinex Cloud
DELog inSign up
Docker CE
Containers

Docker CE

Docker Engine on Ubuntu 24.04, ready for your containers.

Docker Engine and the Docker Compose plugin preinstalled on Ubuntu 24.04 LTS. Start containers seconds after the server boots, on your own cloud server in Frankfurt.

Deploy Docker CEGetting started

Opens the Odinex console with Docker CE selected. No licence fee: you pay for the server only.

Base image
Ubuntu 24.04 LTS
Minimum
1 GB RAM · 20 GB disk
Recommended plan
S2 (2 vCPU · 4 GB RAM · 60 GB NVMe)
Ready after boot
About a minute
Image slug
docker-ce

About Docker CE

Docker CE is the community edition of Docker Engine, the standard runtime for building and running containers. This image is Ubuntu 24.04 LTS with Docker Engine, containerd and the Docker Compose plugin installed from Docker's official apt repository, enabled at boot and verified with a test container on first start.

Nothing else runs on the server and no ports are opened besides SSH: it is a clean, ready host for whatever you want to run, whether a single container, a Compose project or a build agent.

What’s included

Software installed on the image and the ports it uses.

Software
ComponentVersion
Ubuntu24.04 LTS
Docker Engine (docker-ce)Latest stable release at image build time
Docker Compose pluginLatest stable release at image build time
containerdFrom Docker's repository
Ports
PortProtocolUsed for
22TCPSSH

Who it’s for

  • Developers who deploy with Docker images or Compose files
  • Teams that need a disposable build, test or CI host
  • Anyone self-hosting tools published on Docker Hub or GHCR

Use cases

  • Containerised web apps and APIs

    Run your application and its database with one compose.yaml, behind a reverse proxy such as Caddy or Traefik.

  • CI runners and build hosts

    Register a GitLab Runner, GitHub Actions runner or Buildkite agent that builds images on a dedicated machine.

  • Self-hosted tools

    Uptime monitors, dashboards, wikis and other open-source tools that ship as container images.

Resources

Docker CE needs at least 1 GB of RAM and a 20 GB disk. Every plan includes an NVMe disk and 20 TB of traffic.

Smallest plan

S1

  • 1 vCPU (shared)
  • 2 GB RAM
  • 40 GB NVMe disk

The smallest plan that meets the minimum.

Recommended

S2

  • 2 vCPU (shared)
  • 4 GB RAM
  • 60 GB NVMe disk

A comfortable size for regular use.

Size the server for the containers you plan to run. S1 is enough for a few small services; build hosts benefit from more vCPUs, such as C2. You can resize the server later. See current prices.

Getting started after deploy

  1. Connect over SSH

    When the server is running, connect as root with your SSH key or the root password shown at creation.

    ssh [email protected]

  2. Check the installation

    Docker is already running. The login message shows the installed version.

    docker version
docker run --rm hello-world

  3. Start your first project

    Put a compose.yaml in a folder and start it in the background.

    mkdir -p /srv/app && cd /srv/app
# add compose.yaml
docker compose up -d

  4. Protect published ports

    Every port you publish with -p or ports: is reachable from the internet unless a firewall blocks it. Apply an Odinex firewall that allows only the ports you mean to expose.

Security notes

  • A server without a firewall accepts all inbound traffic. Create an Odinex firewall that allows only SSH (22) and the ports your containers publish and apply it to the server. Odinex firewalls filter traffic before it reaches the server, so Docker's own iptables rules cannot bypass them.
  • Container logs are rotated (json-file driver, 3 files of 20 MB per container), so logs cannot fill a small disk.
  • Use SSH keys rather than a password. When a server is created with an SSH key, password login over SSH is turned off.
  • Keep Docker and the OS current with apt update && apt upgrade; Docker's repository is already configured.

Docker CE questions

Clear answers about location, infrastructure and billing.

Is Docker Compose included?
Yes. The Compose plugin is installed, so docker compose (with a space) works out of the box.
Does Docker bypass the firewall?
Docker rewrites iptables inside the server, which is why UFW rules do not protect published ports. Odinex firewalls are applied outside the server, so they still filter traffic to your containers.
Can I add a volume for container data?
Yes. Attach an Odinex volume, mount it (for example at /srv) and point your bind mounts or Docker's data root at it. Volumes survive a rebuild of the server.
Is there a web interface?
No. This image is plain Docker. If you want a web dashboard and Git deployments, look at Coolify in the marketplace.

Documentation

Docker CE

Odinex Cloud

More from the marketplace

Deploy Docker CE in Frankfurt

Your own server with full root access, NVMe storage and 20 TB of traffic, billed by the hour.

Deploy Docker CEAll apps