cloudflare-tunnel ghcr.io/prophetse7en/cloudflare-tunnel:latest https://github.com/prophetse7en/cloudflare-tunnel/pkgs/container/cloudflare-tunnel latest Tracks upstream cloudflare/cloudflared:latest with healthcheck added bridge false https://discordapp.com/channels/492590071455940612/1486391669384417300 https://github.com/cloudflare/cloudflared Cloudflare Tunnel client with built-in Docker healthcheck. Identical to the official cloudflare/cloudflared image — the only addition is a HEALTHCHECK instruction using the built-in cloudflared tunnel ready command. No files changed, no packages added, no ports opened. Why this exists: The official image uses a distroless base with no shell (/bin/sh). Docker's --health-cmd always runs through /bin/sh, so healthchecks added via Extra Parameters will always fail. This image bakes the healthcheck in using exec-form, which bypasses the shell. Setup: 1. Go to Cloudflare Zero Trust dashboard (dash.teams.cloudflare.com) 2. Navigate to Networks > Tunnels > Create a tunnel 3. Select Cloudflared as connector, give it a name 4. Choose Docker as the environment — Cloudflare shows you a token 5. Copy the token and paste it in Post Arguments below, replacing YOUR_TUNNEL_TOKEN_HERE 6. The TUNNEL_METRICS variable is already set — this is required for the healthcheck 7. Start the container — it should show as healthy within 30 seconds Network:Other https://raw.githubusercontent.com/prophetse7en/unraid-templates/main/cloudflare-tunnel.xml https://raw.githubusercontent.com/prophetse7en/cloudflare-tunnel/main/cloudflare-icon.png tunnel --no-autoupdate run --token YOUR_TUNNEL_TOKEN_HERE Cloudflare Tunnel client with built-in Docker healthcheck. Identical to the official cloudflare/cloudflared image — only a HEALTHCHECK instruction is added. Requires TUNNEL_METRICS environment variable for the healthcheck to work. 0.0.0.0:60123