Self-host Woodpecker CI on a VPS

A simple, container-native CI engine with a server and an agent, driven by pipelines in your repo.

levelrail-cli templates deploy woodpecker --name my-woodpecker

Specification

Status
Listed
Category
Developer Tools
Services
woodpecker-agent, woodpecker-server
Ports
8000
Volumes
1
Memory
about 512 MiB
arm64
image published
amd64
image published
Settings to fill in
none

About Woodpecker CI

A simple, container-native CI engine with a server and an agent, driven by pipelines in your repo. Runs 2 containers (woodpecker-agent, woodpecker-server), with woodpecker-server listening on port 8000; data is kept in named volumes.

What it deploys

Woodpecker CI runs as 2 services in a single Compose app, listening on port 8000, with 1 named volume mount.

ServiceImageTagPortsVolumes
woodpecker-agent woodpeckerci/woodpecker-agent v3.18.1 none none
woodpecker-server woodpeckerci/woodpecker-server v3.18.1 8000 woodpecker_data -> /var/lib/woodpecker

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8000 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. 2 secrets are generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
woodpecker-agentWOODPECKER_AGENT_SECRETGenerated at deploy
woodpecker-agentWOODPECKER_SERVERPreset by the template
woodpecker-serverWOODPECKER_ADMINPreset by the template
woodpecker-serverWOODPECKER_AGENT_SECRETGenerated at deploy
woodpecker-serverWOODPECKER_GITEAPreset by the template
woodpecker-serverWOODPECKER_GITEA_CLIENTPreset by the template
woodpecker-serverWOODPECKER_GITEA_SECRETPreset by the template
woodpecker-serverWOODPECKER_GITEA_URLPreset by the template
woodpecker-serverWOODPECKER_HOSTPreset by the template
woodpecker-serverWOODPECKER_OPENPreset by the template

Install Woodpecker CI on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get woodpecker
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy woodpecker --name my-woodpecker

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Woodpecker CI.

More in Developer Tools

All Developer Tools templates