How to Self-Host Woodpecker CI Lightweight Continuous Integration on VPS

Introduction to Architecture & Core Concepts

Woodpecker CI is a highly efficient, community-driven Continuous Integration engine forked from the Drone CI project. Operating entirely on Docker, Woodpecker utilizes a Server/Agent architecture. The server manages webhooks and the UI, while ephemeral agents execute the actual build pipelines inside isolated Docker containers. This ensures completely reproducible builds defined declaratively via a .woodpecker.yml file residing in your Git repository.

Under the Hood: Process Threading and Socket Architecture

When engineering high-availability topologies, administrators must comprehend how the host processes system calls, threading, and asynchronous I/O interfaces like io_uring or epoll. Standard monolithic software architectures block I/O operations, meaning a single network delay freezes an entire execution thread. Modern software paradigms inherently bypass this limitation. By multiplexing thousands of non-blocking sockets onto a handful of active CPU event loops, the underlying runtime engine ensures that network latency never impacts processing throughput. Furthermore, allocating specific NUMA (Non-Uniform Memory Access) nodes strictly to isolated processes guarantees that CPU cache thrashing is minimized. In distributed Linux environments, this micro-level tuning differentiates an amateur deployment from a truly resilient, carrier-grade service.

Consider the impact of the C-groups (Control Groups) v2 implementation in modern systemd environments. By strictly partitioning CPU quotas and enforcing hard memory limits at the hypervisor or container runtime layer, we completely neutralize noisy-neighbor scenarios. If a specific subprocess experiences a memory leak or a catastrophic thread starvation event, the kernel aggressively terminates the offending control group, instantly shielding the underlying host operating system from kernel panics.

Hardware Sizing & Prerequisite Checklist

Before embarking on the installation phase, verify your hardware capabilities. Insufficient resource allocation is the leading cause of random process termination.

System Performance & Benchmark Comparison

Before moving workloads to production, consider the hardware scaling matrices and expected latency overheads across varied compute configurations.

Storage subsystem IOPS dictates ultimate database throughput. While CPU dictates parsing speed, write-heavy architectures inherently bottleneck at the block-storage layer. Always provision PCIe 4.0 NVMe storage block devices rather than legacy SSDs for heavy infrastructural components.

Advanced Linux Kernel Tuning for High-Performance Workloads

To extract the absolute maximum performance from your Linux VPS, standard kernel parameters often fall short, particularly for high-throughput or connection-heavy services. The default settings prioritize general-purpose desktop stability over aggressive server performance. We must modify the sysctl configuration to optimize the TCP/IP stack, file descriptors, and virtual memory subsystem.

# Edit /etc/sysctl.d/99-custom-server.conf
# Maximize file descriptors for heavy network sockets
fs.file-max = 2097152
fs.nr_open = 2097152

# TCP BBR Congestion Control for reduced latency
net.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = bbr

# TCP keepalive tuning for stale connection termination
net.ipv4.tcp_keepalive_time = 300
net.ipv4.tcp_keepalive_intvl = 30
net.ipv4.tcp_keepalive_probes = 5

# Ephemeral port exhaustion prevention
net.ipv4.ip_local_port_range = 1024 65535
net.ipv4.tcp_max_syn_backlog = 65535
net.core.somaxconn = 65535

# Swap reduction for database stability
vm.swappiness = 1
vm.dirty_ratio = 15
vm.dirty_background_ratio = 5

Apply these changes immediately across the system architecture without requiring a hard reboot by running sysctl --system. The BBR congestion control algorithm significantly reduces packet loss queuing over long-distance WAN links, which is critical for geographically distributed users accessing your infrastructure. Concurrently, dropping vm.swappiness prevents the Linux Out-Of-Memory (OOM) killer from prematurely evicting vital application memory pages to slow disk-based swap space.

Step-by-Step Linux Installation & Configuration

Woodpecker requires integration with an upstream Git forge (Gitea, GitHub, GitLab, etc.) via OAuth applications to establish trust and intercept repository webhook push events. Once your OAuth client ID and Secret are generated on your forge, deploy the Woodpecker Server and Agent.

# docker-compose.yml configuration
services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    ports:
      - 8000:8000
    volumes:
      - server-data:/var/lib/woodpecker/
    environment:
      - WOODPECKER_HOST=https://ci.yourdomain.com
      - WOODPECKER_GITHUB=true
      - WOODPECKER_GITHUB_CLIENT=oauth_client_id
      - WOODPECKER_GITHUB_SECRET=oauth_secret_key
      - WOODPECKER_AGENT_SECRET=shared_secret_string

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000
      - WOODPECKER_AGENT_SECRET=shared_secret_string

The critical element here is mounting /var/run/docker.sock into the agent. This Docker-out-of-Docker (DooD) pattern allows the agent container to instruct the host Docker daemon to spin up the necessary compilation environments (e.g., Node, Golang, Maven containers) defined in your pipeline configurations.

Enterprise-Grade Security Hardening & UFW Firewall Implementation

Deploying public-facing infrastructure demands a rigorous approach to network security. The Uncomplicated Firewall (UFW) acts as your primary network defense perimeter. Furthermore, we mandate the usage of Fail2Ban to parse systemd journal logs and dynamically ban malicious IP subnets attempting brute-force authentication attacks.

# Enforce default drop policies at the kernel level
ufw default deny incoming
ufw default allow outgoing

# Whitelist strictly necessary administrative and web ports
ufw allow 22/tcp  # SSH (Consider moving to a non-standard port like 2222)
ufw allow 80/tcp  # HTTP ACME challenges
ufw allow 443/tcp # HTTPS TLS traffic

# Reload and enable the ruleset
ufw enable
ufw status numbered

Beyond port filtering, secure the internal UNIX socket permissions. Ensure that the application daemon operates under a dedicated, non-root service account (e.g., useradd -r -s /bin/false app_svc). Avoid utilizing root for any operational binary execution. For cryptographic transit security, integrate Let’s Encrypt TLS 1.3 certificates via Certbot or Caddy, disabling legacy TLS 1.0/1.1 protocols entirely in your reverse proxy configuration.

Real-World Troubleshooting FAQ

Q: Why does the Woodpecker Agent need access to docker.sock?

A: The agent acts as a controller. When a pipeline runs, the agent parses the YAML and asks the host Docker daemon to download and run the specific images (like `node:18` or `golang:1.20`) required for that pipeline step. Without the socket, the agent cannot spawn these worker containers.

Q: Can I run Woodpecker Agents on different physical servers?

A: Yes, this is a major architectural advantage. The Server component is lightweight. You can deploy Agents on completely separate, highly provisioned bare-metal servers. The Agents connect back to the Server via gRPC on port 9000 using the WOODPECKER_AGENT_SECRET for authorization.