Erisa/cloudflared-docker
Erisa/cloudflared-docker has 201 GitHub stars and 31 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-16 20:16 UTC. Last push 2026-10-20.
Measured star growth
- in 24h
- 0
- in 7 days
- Update delayed
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Simple Alpine-built scratch-runtime Dockerfile for cloudflared, with support for multiple architectures.
Developer ToolsREADME.md
OriginalErisa's Cloudflared Docker Image
This repository contains a simple Dockerfile to build cloudflared, the client for Cloudflare Tunnel, from source.
[!NOTE] This Docker image is not an official Cloudflare product.
The aim is to support multiple architectures.
The public image currently supports:
| Docker target | Also known as | Notes |
|---|---|---|
linux/amd64 |
x86_64 |
Majority of modern PCs and servers. |
linux/386 |
x86 |
32-bit Intel/AMD CPUs. Typically really old computer hardware. These images are untested. |
linux/arm64 |
aarch64 |
64-bit ARM hardware. For example Apple Silicon or Raspberry Pi 2/3/4 running a 64-bit OS. |
linux/arm/v7 |
armhf |
32-bit ARM hardware. For example most Raspberry Pi models running Raspberry Pi OS. |
linux/arm/v6 |
armel |
Older 32-bit ARM hardware. Mostly Raspberry Pi 1/0/0W but there may be others. |
linux/s390x |
IBM Z |
Linux on IBM Z for IBM mainframes, most notably IBM Cloud. |
linux/ppc64le |
ppc64el |
Tested on IBM Cloud Power Systems Virtual Server |
linux/riscv64 |
riscv64 |
CPUs from the future. Tested on Scaleway Labs RV1. |
The public image corresponding to this Dockerfile is erisamoe/cloudflared and should work in mostly the same way as the official image.
[!NOTE] If you have any problems or questions with this image, either open a GitHub Issue or join the Cloudflare Developers Discord Server and ping
@Erisain#general-help,#general-discussionsor#off-topicwith your question.
Cloudflare Tunnel
Dashboard setup (Recommended)
A docker-compose example with a Zero Trust dashboard setup would be:
services:
cloudflared:
image: erisamoe/cloudflared
restart: unless-stopped
command: tunnel run
environment:
- TUNNEL_TOKEN=${TUNNEL_TOKEN}
depends_on:
- mycontainer
Where an .env file in the same directory contains TUNNEL_TOKEN= set to the token given by the Zero Trust dashboard.
For more information see the Cloudflare Blog
Note A previous version of this README recommended using
--token ${CLOUDFLARED_TOKEN}, which is a less secure way of handing off the token. Setting theTUNNEL_TOKENvariable seems to be a better way of approaching this.
Config file setup (Named tunnel)
An example for a setup with a local config would be:
services:
cloudflared:
image: erisamoe/cloudflared
restart: unless-stopped # or 'always' to survive container stops
volumes:
- ./cloudflared:/etc/cloudflared
command: tunnel run mytunnel
depends_on:
- mycontainer
Where ./cloudflared is a folder containing the .json or .pem credentials and config.yml for a tunnel.
An example config.yml might look like:
tunnel: uuid-for-tunnel
#Optional
#credentials-file: /etc/cloudflared/uuid-for-tunnel.json
ingress:
- hostname: mywebsite.com
service: http://nginx:80
- service: http_status:404
For more information, refer to the Cloudflare Documentation
To acquire a certificate, you'll need to use the login command.
This will spit out /.cloudflared/cert.pem, rather than /etc/cloudflared.
As such, usage would be something like:
docker run -v $PWD/cloudflared:/.cloudflared erisamoe/cloudflared login
to create a folder called cloudflared in your current dir and deposit a cert.pem into it.
To create a tunnel, you can then do:
docker run -v $PWD/cloudflared:/etc/cloudflared erisamoe/cloudflared tunnel create mytunnel
Which gives you a UUID for the new tunnel and and a .json credentials file corresponding to it.
And now you can either use the above compose example or for testing simply just:
docker run -v $PWD/cloudflared:/etc/cloudflared erisamoe/cloudflared --hostname test.example.com --name mytunnel --hello-world
Which will start up a "Hello world" test tunnel on https://test.example.com.
DNS-over-HTTPS
While not the original intent behind the image, you can also use this to host a DNS resolver that speaks to a DNS-over-HTTPS backend.
For example:
docker run -d -p 53:53/udp --name my-dns-forwarder erisamoe/cloudflared proxy-dns --address 0.0.0.0
Would create a container called my-dns-forwarder that responds to DNS requests on your host.
Keep in mind when using this on a public server (e.g. VPS) it will by default listen on all interfaces, making you a public DNS resolver on the internet.
You can sidestep this by changing the -p to instead be -p 127.0.0.01:53:53/udp to listen on localhost instead.
You can also add upstreams with --upstream https://dns.example.com for example. By default, Cloudflare DNS is used.