Self-host PrivateBin with Levelrail

Verified

A minimalist, encrypted pastebin where the server has zero knowledge of what you paste.

  • AuthorPrivateBinVerified by Levelrail
  • LicenceZlib
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host PrivateBin

  1. Pull the images

    One image is pulled on your server.

    Show images
    • privatebin/nginx-fpm-alpine:1.7.4
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.

  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.

PrivateBin requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Zlib, permissive license
  • Verified. Verified on arm64 with image tag 1.7.4. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 8080 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 PrivateBin. 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 PrivateBin docs page.

Deploy PrivateBin your way

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

Deploy PrivateBin from the CLI

levelrail-cli templates deploy privatebin --name my-privatebin

Deploy PrivateBin 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/privatebin/deploy

PrivateBin configuration

PrivateBin services

ServiceImagePortsVolumes
privatebin privatebin/nginx-fpm-alpine:1.7.4 8080 privatebin_data -> /srv/data

PrivateBin environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8080
Volumes
1 named mount: privatebin_data -> /srv/data

PrivateBin FAQ

How much memory does PrivateBin need?

The catalog lists about 128 MiB of memory for PrivateBin.

Does PrivateBin run on arm64?

For PrivateBin, arm64 is tested; amd64 is image published.

What licence is PrivateBin under?

PrivateBin is licensed under Zlib, which is permissive, with few conditions on reuse.

Does PrivateBin need configuration before it starts?

No. The template fills in its own defaults.

Which ports does PrivateBin use?

PrivateBin listens on port 8080 inside the stack.

Where does PrivateBin keep its data?

In a named volume: privatebin_data mounted at /srv/data.

Can I deploy PrivateBin on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id privatebin for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image privatebin/nginx-fpm-alpine:1.7.4 is what you deploy there.

levelrail-cli templates deploy privatebin --name my-privatebin