I’ve been trying to get a hang of Docker off late, but not making much headway. I work best when I have a task to work towards so all this reading up isn’t getting anywhere. Initially I thought I’d try and do Docker for everything I need to do, but that seemed pointless. I don’t really need the “overhead” of Docker in my life – it’s just an extra layer to keep track of and tweak, and so I didn’t feel like setting up any task for myself with Docker. If I can run a web server directly on one of my VMs, why bother with putting it in a container instead. Of course I can see the use of Docker for developers etc., but I am not a developer\/ too much of a luddite\/ too old for this $hit I guess.\u00a0<\/p>\n
As of now I use Docker containers like throwaway VMs. If I need to try out something, rather than snapshot my VM and do the thing I want to do and then revert snapshot nowadays I’ll just run a container and do what I want to in that and then throw it. Easy peasy.\u00a0<\/p>\n
Today I thought I’d take a stab at using Docker for Pi-Hole. Yes, I could just use Pi-Hole on my Raspberry Pi4 directly, but putting it in a container seemed interesting. I’ve got this new Pi 4 that I setup last week and I am thinking I’ll keep it “clean” and not install much stuff to it directly. By using containers I can do just that. I guess it’s because at the back of my head I have a feeling the Pi 4 could die any time due to over-heating and I’d rather have all the apps & config I run on it kept separate so if things go bad I can easily redo stuff. One advantage of using Docker is that I can keep all my config and data in one place and simply map it into the container at the location the running program wants things to be at, so I don’t have to keep track of many locations.\u00a0<\/p>\n
Anyways, enough talk. Pi-Hole has a GitHub repo<\/a> with it’s Docker stuff. There’s a Docker-compose example as well as a script to run the container<\/a> manually. What I am about to post here is based on that with some modifications for my environment, so there’s nothing new or fancy here …<\/p>\n First thing is that I decided to go with a macvlan network. This too is something I learnt from the Pi-Hole Docker documentation<\/a>. You see, typically your Docker containers are bridged – i.e. they run in an isolated network behind the host running the containers, and only whatever ports you decide to forward on are passed in to this network. It’s exactly like how all the machines in your home network are behind a router and have their own private IP space independent of the Internet, but you can selectively port forward from the public IP of the router to machines in your network.\u00a0<\/p>\n The alternatives to bridged more are host mode, wherein the container has the IP of the host and all its ports; or macvlan mode, wherein the container appears as a separate device on your network. (It’s sort of like how in something like Hyper-V you can have a VM to be on an “external” network – it appears as a device connected to the same network as the host and has its own IP address etc). I like this latter idea, maybe coz it ties into my tendency to use a container as a VM. :) In the specific case of Pi-Hole in Docker going the macvlan has an advantage in that the Pi-Hole can act like a DHCP server and send out broadcasts as it is on the network like any other device, and not hidden behind the machine running the container.\u00a0<\/p>\n So first things first, I created a macvlan network for myself. This also requires you to specify your network subnet and gateway because remember Docker assigns all its containers IP addresses and so you need to tell Docker to assign an IP address from such and such network. In my case I am not really going to let Docker assign an IP address later because I’ll just specify one manually, but the Next thing is to create some volumes to store data. I could go with bind mounts or volumes – the latter is where Docker manages the volumes. I chose to go with volumes. Docker will store all these volumes at Lastly here’s the Again, replace all the variables with appropriate info for your environment. These lines may be of interest as they map the network and volumes I created earlier into the container, and also specify a static IP like I said I’d do.\u00a0<\/p>\n Everything else is from the official instructions, with the exception of That’s it, now I’ll have Pi-Hole running at Here’s everything together in case it helps (I have this in a shell script actually with the variables defined so I can re-run the script if needed; Docker won’t create the volumes and networks again if they already exist):<\/p>\n Now this is a cool feature of Docker. After running the above I can run this command to set the admin password:\u00a0<\/p>\n What’s cool about this is that I am simply running a command in the container as if it were a program on my machine. For some reason I find that awesome. You are encapsulating an entire container as a single command<\/em>. What the above does is that it runs the I’ve been trying to get a hang of Docker off late, but not making much headway. I work best when I have a task to work towards so all this reading up isn’t getting anywhere. Initially I thought I’d try and do Docker for everything I need to do, but that seemed pointless. I don’t … Continue reading Pi-Hole Docker<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[912,333],"tags":[498,907],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/4741"}],"collection":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/comments?post=4741"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/4741\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=4741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=4741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=4741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}network create<\/code> command expects a range when making a macvlan network so I oblige it (replace the $SUBNET<\/code> and $GATEWAY<\/code> variables below with your environment details, the subnet has to be in the CIDR notation e.g. 192.168.1.0\/24). I have to also specify which device on the Raspberry Pi the macvlan network will connect to so I do that via the -o parent<\/code> switch. And finally I give it an unimaginative name my_macvlan_network<\/code>.\u00a0<\/p>\ndocker network create -d macvlan \\\n --subnet=\"$SUBNET\" \\\n --gateway=\"$GATEWAY\" \\\n -o parent=eth0 \\\n my_macvlan_network<\/pre>\n
\/var\/lib\/docker\/volumes\/<\/code> so that’s the only location I need to backup. From the GitHub repo I saw it expects two locations, so I created two volumes for use later on.<\/p>\ndocker volume create my_pihole\ndocker volume create my_dnsmasq<\/pre>\n
docker run<\/code> command, based on the one found on GitHub:<\/p>\ndocker run -d \\\n --name my_pihole \\\n --ip=\"$IP\" \\\n --network=\"my_macvlan_network\" \\\n -v my_pihole:\/etc\/pihole\/ \\\n -v my_dnsmasq:\/etc\/dnsmasq.d\/ \\\n --dns=127.0.0.1 --dns=1.1.1.1 \\\n --restart=unless-stopped \\\n --hostname $HOSTNAME \\\n -e TZ=\"Europe\/London\" \\\n -e VIRTUAL_HOST=\"$HOSTNAME\" \\\n -e PROXY_LOCATION=\"$HOSTNAME\" \\\n -e SERVER_IP=\"$IP\" \\\n --cap-add=NET_ADMIN \\\n pihole\/pihole:latest<\/pre>\n
--ip=\"$IP\" \\\n --network=\"my_macvlan_network\" \\\n -v my_pihole:\/etc\/pihole\/ \\\n -v my_dnsmasq:\/etc\/dnsmasq.d\/ \\<\/pre>\n
--cap-add=NET_ADMIN<\/code> which I have to do to give the container additional capabilities (required if you plan on running it as a DHCP server).\u00a0<\/p>\n$IP<\/code>.\u00a0<\/p>\n# create the macvlan network\n# I call it my_macvlan_network, point it to my subnet and interface\n# I am not excluding any IPs for now as I'll be assigning the container an IP myself\ndocker network create -d macvlan \\\n --subnet=\"$SUBNET\" \\\n --gateway=\"$GATEWAY\" \\\n -o parent=eth0 \\\n my_macvlan_network\n\n# create volumes\ndocker volume create my_pihole\ndocker volume create my_dnsmasq\n\ndocker run -d \\\n --name my_pihole \\\n --ip=\"$IP\" \\\n --network=\"my_macvlan_network\" \\\n -v my_pihole:\/etc\/pihole\/ \\\n -v my_dnsmasq:\/etc\/dnsmasq.d\/ \\\n --dns=127.0.0.1 --dns=1.1.1.1 \\\n --restart=unless-stopped \\\n --hostname $HOSTNAME \\\n -e TZ=\"Europe\/London\" \\\n -e VIRTUAL_HOST=\"$HOSTNAME\" \\\n -e PROXY_LOCATION=\"$HOSTNAME\" \\\n -e SERVER_IP=\"$IP\" \\\n --cap-add=NET_ADMIN \\\n pihole\/pihole:latest\n\n # I got the TZ info from running 'tzselect' and noting the final output once I selected the timezone.\n # I use --network to specify a macvlan network & --ip to specify an IP. Since I am using a macvlan I don't need to publish any ports. \n # --cap-add=NET_ADMIN needed for DHCP<\/pre>\n
docker exec -it pihole pihole -a -p<\/pre>\n
pihole -a -p<\/code> command in the container called pihole<\/code>. This command prompts me for an admin username, and since I have the -it<\/code> switch added to the exec<\/code> command it tells Docker that I want an interactive session and that it should map STDIN and STDOUT of the container to my host and thus show me the output and let me type and pass in some input. So cool!\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"