Skip to content

run the cloudflared proxy-dns on port 54 using the DNS over HTTPS feature from cloudflare.

License

Notifications You must be signed in to change notification settings

H4R0/dockerfile-cloudflared

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Cloudflared

Build Status License Docker Pulls

a docker container which runs the cloudflared proxy-dns at port 5054 based on alpine with some parameters to enable DNS over HTTPS proxy for pi-hole based on tutorials from Oliver Hough and Scott Helme

run

docker run --name cloudflared --rm --net host visibilityspots/cloudflared

run with docker-compose

docker-compose up -d

custom upstream DNS

docker run --name cloudflared --rm --net host -e DNS1=#.#.#.# -e DNS2=#.#.#.# visibilityspots/cloudflared

custom port

docker run --name cloudflared --rm --net host -e PORT=5053 visibilityspots/cloudflared

dualstack ipv4/ipv6

docker run --name cloudflared --rm --net host -e ADDRESS :: visibilityspots/cloudflared

test

I wrote some tests in a goss.yaml file which can be executed by dgoss

$ dgoss run --name cloudflared --rm -ti visibilityspots/cloudflared:latest
INFO: Starting docker container
INFO: Container ID: e5bd35d3
INFO: Sleeping for 0.2
INFO: Running Tests
Process: cloudflared: running: matches expectation: [true]
Package: ca-certificates: installed: matches expectation: [true]
Command: cloudflared --version | head -1: exit-status: matches expectation: [0]
Command: cloudflared --version | head -1: stdout: matches expectation: [cloudflared version DEV (built unknown)]


Total Duration: 0.028s
Count: 4, Failed: 0, Skipped: 0
INFO: Deleting container

License

Distributed under the MIT license

About

run the cloudflared proxy-dns on port 54 using the DNS over HTTPS feature from cloudflare.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Dockerfile 100.0%