How to Self-Host Drone CI: Container-Native CI/CD 2026

TL;DR

Drone CI (Apache 2.0, ~31K GitHub stars, Go) is a container-native CI/CD platform designed for self-hosting. Every build step runs inside a Docker container — no more Jenkins plugins or brittle agent configurations. Pipelines are defined in .drone.yml (YAML), runners execute Docker containers on your hardware, and the server is a single lightweight Go binary. Works with Gitea, GitHub, GitLab, Bitbucket, and Gitea/Forgejo out of the box via OAuth2.

Key Takeaways

Drone CI: Apache 2.0, ~31K stars, Go — Docker-native CI/CD, one YAML per repo
Container-first: Every step runs in its own Docker container — fully reproducible builds
Gitea native: First-class Gitea/Forgejo integration via OAuth2
Secrets management: Encrypted secrets per-repo or org-wide
Multi-runner: Scale by adding more Docker runners on any machine
Exec runner: For builds that need bare-metal access (not in Docker)

Drone vs Woodpecker vs Gitea Actions

Feature	Drone CI	Woodpecker CI	Gitea Actions
License	Apache 2.0	Apache 2.0	Built-in
GitHub Stars	~31K	~4K	—
Pipeline format	Drone YAML	Woodpecker YAML	GitHub Actions YAML
GitHub Actions compat	No	Partial	Yes
Multi-runner	Yes	Yes	Yes
Docker runner	Yes	Yes	Yes
Bare-metal runner	Yes (exec)	Yes	Yes
Secrets	Encrypted	Encrypted	Encrypted
Parallelism	Yes	Yes	Yes
Best with	Gitea/GitHub	Gitea/Forgejo	Gitea/Forgejo

Part 1: Docker Setup

# docker-compose.yml
services:
  drone:
    image: drone/drone:latest
    container_name: drone
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - drone_data:/data
    environment:
      # Gitea OAuth2 integration:
      DRONE_GITEA_SERVER: "https://git.yourdomain.com"
      DRONE_GITEA_CLIENT_ID: "${GITEA_CLIENT_ID}"
      DRONE_GITEA_CLIENT_SECRET: "${GITEA_CLIENT_SECRET}"
      # Drone server config:
      DRONE_RPC_SECRET: "${DRONE_RPC_SECRET}"
      DRONE_SERVER_HOST: "ci.yourdomain.com"
      DRONE_SERVER_PROTO: "https"
      DRONE_TLS_AUTOCERT: "false"
      # Admin user (your Gitea username):
      DRONE_USER_CREATE: "username:admin,admin:true"
      # Database:
      DRONE_DATABASE_DATASOURCE: "/data/database.sqlite"
      DRONE_DATABASE_DRIVER: "sqlite3"

volumes:
  drone_data:

# .env
DRONE_RPC_SECRET=$(openssl rand -hex 16)
# GITEA_CLIENT_ID and GITEA_CLIENT_SECRET from Gitea OAuth2 app setup below

docker compose up -d

Part 2: HTTPS with Caddy

ci.yourdomain.com {
    reverse_proxy localhost:8080
}

Part 3: Gitea OAuth2 Setup

Create an OAuth2 application in Gitea for Drone:

Gitea: User Settings → Applications → OAuth2 Applications → Create OAuth2 Application
Application Name: Drone CI
Redirect URI: https://ci.yourdomain.com/login
Copy Client ID and Client Secret to .env

Part 4: Add a Docker Runner

The server only coordinates — runners do the actual build work:

# Add to docker-compose.yml:
services:
  drone-runner:
    image: drone/drone-runner-docker:latest
    container_name: drone_runner
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      DRONE_RPC_PROTO: "https"
      DRONE_RPC_HOST: "ci.yourdomain.com"
      DRONE_RPC_SECRET: "${DRONE_RPC_SECRET}"
      DRONE_RUNNER_CAPACITY: 2          # Concurrent builds
      DRONE_RUNNER_NAME: "docker-runner-1"
      DRONE_LOGS_TRACE: "false"

# Scale runners on additional machines:
docker run -d \
  -e DRONE_RPC_PROTO=https \
  -e DRONE_RPC_HOST=ci.yourdomain.com \
  -e DRONE_RPC_SECRET=your-rpc-secret \
  -e DRONE_RUNNER_CAPACITY=4 \
  -e DRONE_RUNNER_NAME=worker-2 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  drone/drone-runner-docker:latest

Part 5: Pipeline YAML

Create .drone.yml in your repository root:

Basic pipeline

# .drone.yml
kind: pipeline
type: docker
name: default

steps:
  - name: test
    image: node:20-alpine
    commands:
      - npm ci
      - npm test

  - name: build
    image: node:20-alpine
    commands:
      - npm run build
    when:
      branch:
        - main

Multi-stage with Docker build

kind: pipeline
type: docker
name: default

steps:
  - name: test
    image: python:3.12-slim
    commands:
      - pip install -r requirements.txt
      - pytest

  - name: build-image
    image: plugins/docker
    settings:
      registry: git.yourdomain.com
      repo: git.yourdomain.com/myorg/myapp
      tags:
        - latest
        - ${DRONE_COMMIT_SHA:0:8}
      username:
        from_secret: docker_username
      password:
        from_secret: docker_password

  - name: deploy
    image: alpine
    commands:
      - apk add --no-cache openssh
      - ssh deploy@prod.yourdomain.com "docker pull git.yourdomain.com/myorg/myapp:latest && docker compose up -d"
    environment:
      SSH_KEY:
        from_secret: deploy_ssh_key
    when:
      branch:
        - main

Parallel steps

kind: pipeline
type: docker
name: default

steps:
  - name: backend-test
    image: python:3.12
    commands:
      - cd backend && pip install -r requirements.txt && pytest

  - name: frontend-test
    image: node:20
    commands:
      - cd frontend && npm ci && npm test

# These two steps run in parallel (different resources, no depends_on)

Trigger conditions

trigger:
  branch:
    - main
    - release/*
  event:
    - push
    - pull_request
    - tag

Part 6: Secrets Management

# Install Drone CLI:
curl -L https://github.com/harness/drone-cli/releases/latest/download/drone_linux_amd64.tar.gz | tar zx
sudo mv drone /usr/local/bin/

# Configure CLI:
export DRONE_SERVER=https://ci.yourdomain.com
export DRONE_TOKEN=your-personal-token   # From Drone UI → Account → Token

# Add secret to a repo:
drone secret add --repository myorg/myrepo \
  --name docker_password \
  --data "your-registry-password"

# List secrets:
drone secret ls --repository myorg/myrepo

# Add org-wide secret:
drone orgsecret add myorg docker_password "your-registry-password"

Use in pipeline:

settings:
  password:
    from_secret: docker_password

Part 7: Exec Runner (Bare-Metal)

For builds that need the host's Docker daemon, GPU, or specific hardware:

# Install exec runner on the build host:
curl -L https://github.com/drone-runners/drone-runner-exec/releases/latest/download/drone_runner_exec_linux_amd64.tar.gz | tar zx
sudo mv drone-runner-exec /usr/local/bin/

# Configure:
sudo mkdir -p /etc/drone-runner-exec
cat > /etc/drone-runner-exec/config << EOF
DRONE_RPC_PROTO=https
DRONE_RPC_HOST=ci.yourdomain.com
DRONE_RPC_SECRET=your-rpc-secret
DRONE_RUNNER_NAME=exec-runner
DRONE_RUNNER_CAPACITY=1
EOF

# Run as systemd service:
sudo drone-runner-exec service install
sudo drone-runner-exec service start

# Pipeline targeting exec runner:
kind: pipeline
type: exec
name: gpu-build

platform:
  os: linux
  arch: amd64

steps:
  - name: train
    commands:
      - python train.py --gpu

Maintenance

# Update Drone:
docker compose pull
docker compose up -d

# Backup:
tar -czf drone-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect drone_drone_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f drone
docker compose logs -f drone-runner

# Check runner status:
curl -s https://ci.yourdomain.com/api/runners \
  -H "Authorization: Bearer your-admin-token" | jq

Why Self-Host Drone CI?

The case for self-hosting Drone CI comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Drone CI means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Drone CI, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Drone CI headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Drone CI data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Drone CI without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Drone CI's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Drone CI backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Drone CI's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Drone CI's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Drone CI's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Drone CI's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f drone

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Drone CI's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats drone. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Drone CI Updated

Drone CI follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Drone CI is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

Frequently Asked Questions

How much does it cost to self-host Drone CI?

The primary cost is your server. A Hetzner CAX11 (2 vCPU ARM, 4GB RAM) runs about $5/month — enough for Drone CI plus a few companion services. Add a domain ($12/year) and you're under $75/year for a complete self-hosted deployment. Compare that to SaaS pricing that typically starts at $5-15/user/month.

Can I run Drone CI on a VPS with other services?

Yes. The docker-compose.yml above isolates Drone CI on its own named Docker network. As long as your server has sufficient RAM and disk — 4GB RAM and 20GB disk handles most combinations — running multiple self-hosted services on one VPS is both practical and common. Tools like Dozzle and Portainer make monitoring multi-container setups manageable.

How do I migrate data if I switch servers?

Stop the Drone CI container, export the Docker volumes (using docker run --rm -v VOLUME:/data -v $(pwd):/backup alpine tar czf /backup/backup.tar.gz /data), transfer to the new server, restore the volumes, and update your DNS. Most migrations complete in under an hour. Test the restoration on the new server before decommissioning the old one.

What happens if Drone CI releases a breaking update?

Pin your docker-compose.yml to a specific image tag (e.g., image: drone/ci:1.2.3 instead of latest). Subscribe to the GitHub releases page for advance notice. When you're ready to upgrade, read the release notes, back up first, test on a staging instance, then update production.

Is Drone CI suitable for production use?

Yes, with the hardening described above: reverse proxy for HTTPS, firewall rules, regular backups, and a pinned image tag. Many teams run Drone CI in production successfully. The main requirement is treating your self-hosted instance with the same operational discipline you'd apply to any business-critical service.

See all open source CI/CD and DevOps tools at OSSAlt.com/categories/devops.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)