Self-host Step CA with Levelrail
A private certificate authority that issues and renews TLS and SSH certificates over ACME or a CLI. Apache-2.0 licensed. The CA password is generated for you and shown in the deployment variables.
- Authorsmallstep
- LicenceApache-2.0
- Memory128 MiB
- Services1
How to self-host Step CA
-
Pull the images
One image is pulled on your server.
Show images
smallstep/step-ca:0.30.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9000.
-
Fill in the secrets
1 secret is generated and stored encrypted, 3 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.
After the first start
- Read the root certificate fingerprint from the deployment logs, then bootstrap clients with step ca bootstrap.
Step CA requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9000
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Step CA. 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 Step CA docs page.
Deploy Step CA your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Step CA from the CLI
levelrail-cli templates deploy step-ca --name my-step-ca Deploy Step CA with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/step-ca/deploy Step CA configuration
Step CA services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| step-ca | smallstep/step-ca:0.30.2 | 9000 | step -> /home/step |
Step CA environment variables
| Variable | Service | Value |
|---|---|---|
| DOCKER_STEPCA_INIT_ACME | step-ca | Preset by the template |
| DOCKER_STEPCA_INIT_DNS_NAMES | step-ca | Preset by the template |
| DOCKER_STEPCA_INIT_NAME | step-ca | Preset by the template |
| DOCKER_STEPCA_INIT_PASSWORD | step-ca | Generated at deploy |
Ports and volumes
- Ports
- 9000
- Volumes
- 1 named mount: step -> /home/step
Step CA FAQ
How much memory does Step CA need?
The catalog lists about 128 MiB of memory for Step CA.
Does Step CA run on arm64?
For Step CA, arm64 support is not confirmed; amd64 is unknown.
What licence is Step CA under?
Step CA is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Step CA need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Step CA use?
Step CA listens on port 9000 inside the stack.
Where does Step CA keep its data?
In a named volume: step mounted at /home/step.
Can I deploy Step CA 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 Step CA, 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 smallstep/step-ca:0.30.2 is what you deploy there.