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-woodpeckerSpecification
- 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
- License
- Permissive license, Apache-2.0
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.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| 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.
| Service | Variable | Value |
|---|---|---|
| woodpecker-agent | WOODPECKER_AGENT_SECRET | Generated at deploy |
| woodpecker-agent | WOODPECKER_SERVER | Preset by the template |
| woodpecker-server | WOODPECKER_ADMIN | Preset by the template |
| woodpecker-server | WOODPECKER_AGENT_SECRET | Generated at deploy |
| woodpecker-server | WOODPECKER_GITEA | Preset by the template |
| woodpecker-server | WOODPECKER_GITEA_CLIENT | Preset by the template |
| woodpecker-server | WOODPECKER_GITEA_SECRET | Preset by the template |
| woodpecker-server | WOODPECKER_GITEA_URL | Preset by the template |
| woodpecker-server | WOODPECKER_HOST | Preset by the template |
| woodpecker-server | WOODPECKER_OPEN | Preset by the template |
Install Woodpecker CI on a VPS
-
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 -
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 | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get woodpecker -
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.
Docs and upstream
More in Developer Tools
- WireMockAn HTTP mock server that stubs and records API responses for development and tests. Stubs are managed through its admin API, so restrict who can reach it.
- WeblateA continuous localization system for translating software with a web-based editor and review flow.
- Web CheckAn all-in-one OSINT tool for inspecting a website's DNS, headers, certs, and security posture.
- Zot RegistryOCI native container image registry with a web UI, search and optional sync. The install form carries config.json as an editable file and images are stored on a volume.
- WakapiA self-hosted, WakaTime-compatible backend for tracking coding time and stats.
- VerdaccioA lightweight private npm proxy registry with caching and local package publishing.