Self-host Blocky with Levelrail

DNS proxy and ad blocker with caching and conditional forwarding. The install form carries config.yml as an editable file, so it starts with a small denylist and public upstream resolvers.

  • Author0xERR0R
  • LicenceApache-2.0
  • Memory64 MiB
  • Services1

How to self-host Blocky

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/0xerr0r/blocky:v0.36.0
  2. Create the app

    One service starts in a single Compose app, on ports 4000, 5353.

  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.

After the first start

  • Point a client at the DNS port to resolve through Blocky, then edit the config file setting to add real blocklists. The HTTP API is on port 4000.

Blocky requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
4000, 5353
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 Blocky. 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 Blocky docs page.

Deploy Blocky your way

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

Deploy Blocky from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain blocky=app.example.com.

levelrail-cli templates install blocky --name my-blocky

Deploy Blocky with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/blocky/install \
  -d '{
    "name": "my-blocky"
  }'

Blocky configuration

Blocky services

ServiceImagePortsVolumes
blocky ghcr.io/0xerr0r/blocky:v0.36.0 4000, 5353 none

Blocky environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
4000, 5353
Volumes
none

Blocky FAQ

How much memory does Blocky need?

The catalog lists about 64 MiB of memory for Blocky.

Does Blocky run on arm64?

For Blocky, arm64 support is not confirmed; amd64 is unknown.

What licence is Blocky under?

Blocky is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Blocky need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Blocky use?

Blocky listens on ports 4000 and 5353 inside the stack.

Can I deploy Blocky 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 Blocky, 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 ghcr.io/0xerr0r/blocky:v0.36.0 is what you deploy there.

levelrail-cli templates install blocky --name my-blocky