"Running Docker Containers on Your VPS"

Docker containers have become the standard for packaging and deploying modern applications. A Data Mammoth VPS is an ideal platform for running Docker — you get full root access, dedicated resources, and the flexibility to run any containerized workload. Whether you are deploying a single application or managing a multi-container architecture, this guide covers everything you need to get started.

Why Run Docker on a VPS?

Full Control

Unlike managed container platforms that restrict what images you can run or how you configure networking, a VPS gives you complete control over your Docker environment. Install any version of Docker, use any image, and configure networking and storage exactly as you need.

Cost Effective

Running Docker on a VPS is often more cost-effective than managed container services, especially for small to medium workloads. You pay a fixed monthly price for your VPS resources, with no per-container fees or egress charges.

Flexibility

On a VPS, you can run Docker alongside other services. Mix containerized and non-containerized applications on the same server. Use Docker Compose to define multi-container stacks. Run lightweight Kubernetes distributions for orchestration.

Isolation

Each Docker container runs in its own isolated environment with its own file system, network namespace, and process space. This lets you run multiple applications with different dependencies on the same server without conflicts.

Prerequisites

• A Data Mammoth VPS with at least 2 vCPUs and 4 GB RAM (recommended minimum for Docker workloads).
• A Linux operating system — Ubuntu 22.04 LTS or Debian 12 are recommended. See Available Operating Systems for VPS.
• SSH access to your server. See How to Connect to Your Server via SSH.

Installing Docker

Connect to your server via SSH and install Docker using the official installation method.

Step 1 — Update Your System

Ensure all packages are up to date:

sudo apt update && sudo apt upgrade -y

Step 2 — Install Docker

Install Docker Engine using the official convenience script or package repository. The convenience script is the fastest method:

curl -fsSL https://get.docker.com | sudo sh

Step 3 — Enable Docker

Ensure Docker starts automatically on boot:

sudo systemctl enable docker
sudo systemctl start docker

Step 4 — Verify the Installation

Run the Docker hello-world test:

sudo docker run hello-world

If successful, you will see a message confirming that Docker is installed and working.

Step 5 — Allow Non-Root Access (Optional)

By default, Docker requires root privileges. To run Docker commands without sudo, add your user to the docker group:

sudo usermod -aG docker $USER

Log out and log back in for the change to take effect.

Running Your First Container

Pull and run a container from Docker Hub:

docker run -d -p 80:80 --name my-web-server nginx

This command:

• Downloads the official Nginx image.
• Runs it in the background (-d).
• Maps port 80 on your VPS to port 80 in the container.
• Names the container my-web-server.

Docker Compose for Multi-Container Applications

Most real-world applications consist of multiple services — a web application, a database, a cache, and so on. Docker Compose lets you define and run multi-container applications using a single YAML file.

Install Docker Compose

Docker Compose is typically included with modern Docker installations. Verify:

docker compose version

Create a Docker Compose File

Create a docker-compose.yml file that defines your services. Here is an example for a web application with a database and cache:

services:
  app:
    image: your-application:latest
    ports:
      - "80:3000"
    environment:
      - DATABASE_URL=postgres://user:pass@db:5432/myapp
      - REDIS_URL=redis://cache:6379
    depends_on:
      - db
      - cache
  db:
    image: postgres:16
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_USER=user
      - POSTGRES_PASSWORD=pass
      - POSTGRES_DB=myapp
  cache:
    image: redis:7-alpine
volumes:
  db-data:

Start Your Stack

docker compose up -d

This starts all three services in the background. Docker Compose handles networking between containers automatically — each service can reach the others by name (e.g., db, cache).

Manage Your Stack

• View running containers: docker compose ps
• View logs: docker compose logs -f
• Stop all services: docker compose down
• Rebuild after changes: docker compose up -d --build

Data Persistence with Volumes

Containers are ephemeral — when a container is removed, its data is lost. Use Docker volumes to persist data:

volumes:
  db-data:
    driver: local

Volumes survive container restarts, removals, and updates. Always use volumes for:

• Database data directories
• Application uploads and media
• Configuration files that need to persist

Container Networking

Docker creates an isolated network for each Docker Compose project. Containers within the same project can communicate by service name.

For external access, map container ports to VPS ports using the ports directive. Only expose ports that need to be publicly accessible.

For additional network security, configure your Data Mammoth cloud firewall to allow only the specific ports your containers expose.

Resource Management

Memory Limits

Prevent containers from consuming all server memory by setting limits:

services:
  app:
    image: your-application:latest
    deploy:
      resources:
        limits:
          memory: 512M

CPU Limits

Restrict CPU usage per container:

deploy:
  resources:
    limits:
      cpus: "1.0"

Monitoring

Monitor container resource usage:

docker stats

This shows real-time CPU, memory, network, and disk I/O for each running container.

Security Best Practices

• Do not run containers as root inside the container. Use a non-root user in your Dockerfiles.
• Use official images from Docker Hub or verified publishers.
• Keep images updated to include security patches.
• Do not store secrets in images. Use environment variables or Docker secrets.
• Limit network exposure — only map ports that need external access.
• Scan images for vulnerabilities using tools like Docker Scout or Trivy.

Recommended VPS Specifications for Docker

What to Do Next

• How to Order Your First Server — Deploy a VPS for Docker workloads.
• Optimizing VPS Performance — Tune your server for containerized applications.
• How to Create and Restore VPS Snapshots — Back up before major container changes.
• How to Set Up Cloud Firewall Rules — Secure container port exposure.