Self-host Cockpit CMS with Levelrail

A headless content platform for managing structured content behind a clean API, without a big CMS footprint.

  • Authoragentejo
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host Cockpit CMS

  1. Pull the images

    One image is pulled on your server.

    Show images
    • cockpithq/cockpit:core-latest
  2. Create the app

    One service starts in a single Compose app, with 3 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Cockpit CMS requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, 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 80 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 Cockpit CMS. 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 Cockpit CMS docs page.

Deploy Cockpit CMS your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Cockpit CMS from the CLI

levelrail-cli templates deploy cockpit-cms --name my-cockpit-cms

Deploy Cockpit CMS with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/cockpit-cms/deploy

Cockpit CMS configuration

Cockpit CMS services

ServiceImagePortsVolumes
cockpit-cms cockpithq/cockpit:core-latest 80 cockpitcms_config -> /var/www/html/configcockpitcms_storage -> /var/www/html/storagecockpitcms_spaces -> /var/www/html/.spaces

Cockpit CMS environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
80
Volumes
3 named mounts: cockpitcms_config -> /var/www/html/config, cockpitcms_storage -> /var/www/html/storage, cockpitcms_spaces -> /var/www/html/.spaces

Cockpit CMS FAQ

How much memory does Cockpit CMS need?

The catalog lists about 512 MiB of memory for Cockpit CMS.

Does Cockpit CMS run on arm64?

For Cockpit CMS, an arm64 image is published; amd64 is image published.

What licence is Cockpit CMS under?

Cockpit CMS is licensed under MIT, which is permissive, with few conditions on reuse.

Does Cockpit CMS need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Cockpit CMS use?

Cockpit CMS listens on port 80 inside the stack.

Where does Cockpit CMS keep its data?

In named volumes: cockpitcms_config mounted at /var/www/html/config, cockpitcms_storage mounted at /var/www/html/storage and cockpitcms_spaces mounted at /var/www/html/.spaces.

Can I deploy Cockpit CMS 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 Cockpit CMS, 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 cockpithq/cockpit:core-latest is what you deploy there.

levelrail-cli templates deploy cockpit-cms --name my-cockpit-cms