How do I run Docker on my own Ubuntu server?

For a home server, Docker Engine is the main thing you need. You can download images from a public container registry without paying, although anonymous downloads may have rate limits. Those limits are usually not a problem for normal personal use. Compose is worth learning because it lets you describe services, storage volumes, networks, and settings in one configuration file instead of entering long commands manually.

You can optionally install a web management tool such as Portainer Community Edition if you prefer a browser interface. It makes it easier to view containers, logs, images, and volumes, but it isn’t required. Learning the command line first is still useful because most Docker documentation and troubleshooting steps use it.

Before exposing anything to the internet, secure the server. Keep it behind a router or firewall, avoid forwarding unnecessary ports, use strong authentication, update Ubuntu and Docker regularly, and only publish the ports required by each service. Containers are not a replacement for normal server security.

When Docker runs on your own server, the containers normally use that machine’s CPU, RAM, storage, and network resources. Docker Engine itself is free for typical personal and self-hosted use. Paid plans generally relate to hosted registries, image-pull limits, collaboration features, or commercial support—not basic container execution. Start with Docker’s official Ubuntu installation instructions rather than relying on a generic package command, since Ubuntu’s repository may not provide the newest version. After installing it, try running a simple image, then learn Docker Compose for managing groups of connected containers.