Self-host Woodpecker CI with Levelrail
A simple, container-native CI engine with a server and an agent, driven by pipelines in your repo.
- Authorwoodpecker-ci
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services2
How to self-host Woodpecker CI
-
Pull the images
2 images are pulled on your server.
Show images
woodpeckerci/woodpecker-agent:v3.18.1woodpeckerci/woodpecker-server:v3.18.1
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 8 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Woodpecker CI requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Woodpecker CI. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Woodpecker CI docs page.
Deploy Woodpecker CI your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Woodpecker CI from the CLI
levelrail-cli templates deploy woodpecker --name my-woodpecker Deploy Woodpecker CI with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/woodpecker/deploy Woodpecker CI configuration
Woodpecker CI services
| Service | Image | 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 |
Woodpecker CI environment variables
| Variable | Service | Value |
|---|---|---|
| WOODPECKER_AGENT_SECRET | woodpecker-agent | Generated at deploy |
| WOODPECKER_SERVER | woodpecker-agent | Preset by the template |
| WOODPECKER_ADMIN | woodpecker-server | Preset by the template |
| WOODPECKER_AGENT_SECRET | woodpecker-server | Generated at deploy |
| WOODPECKER_GITEA | woodpecker-server | Preset by the template |
| WOODPECKER_GITEA_CLIENT | woodpecker-server | Preset by the template |
| WOODPECKER_GITEA_SECRET | woodpecker-server | Preset by the template |
| WOODPECKER_GITEA_URL | woodpecker-server | Preset by the template |
Show all 10 variables
- WOODPECKER_HOSTwoodpecker-serverPreset by the template
- WOODPECKER_OPENwoodpecker-serverPreset by the template
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: woodpecker_data -> /var/lib/woodpecker
Woodpecker CI FAQ
How much memory does Woodpecker CI need?
The catalog lists about 512 MiB of memory for Woodpecker CI across its 2 services.
Does Woodpecker CI run on arm64?
For Woodpecker CI, an arm64 image is published; amd64 is image published.
What licence is Woodpecker CI under?
Woodpecker CI is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Woodpecker CI need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Woodpecker CI use?
Woodpecker CI listens on port 8000 inside the stack.
Where does Woodpecker CI keep its data?
In a named volume: woodpecker_data mounted at /var/lib/woodpecker.
Can I deploy Woodpecker CI on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Woodpecker CI, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image woodpeckerci/woodpecker-agent:v3.18.1, woodpeckerci/woodpecker-server:v3.18.1 is what you deploy there.