{"id":4743,"date":"2020-07-27T21:14:39","date_gmt":"2020-07-27T17:14:39","guid":{"rendered":"https:\/\/rakhesh.com\/?p=4743"},"modified":"2020-10-05T18:59:23","modified_gmt":"2020-10-05T17:59:23","slug":"pi-hole-docker-contd","status":"publish","type":"post","link":"https:\/\/rakhesh.com\/infrastructure\/pi-hole-docker-contd\/","title":{"rendered":"Pi-Hole Docker (contd.)"},"content":{"rendered":"

This post isn’t much about Pi-Hole, sorry for the misleading title. It is a continuation to my previous post<\/a> though and I couldn’t think of any other title.\u00a0<\/p>\n

I thought I’d put the docker commands of the previous post into a docker compose YAML file as that seems to be the fashion. Here’s what I ended with before I gave up:<\/p>\n

version: \"2\"\r\n\r\n# From https:\/\/github.com\/pi-hole\/docker-pi-hole\/blob\/master\/README.md\r\n\r\nnetworks:\r\n  my_macvlan_network:\r\n    driver: macvlan\r\n    driver_opts:\r\n      parent: eth0\r\n    ipam:\r\n      config:\r\n        - subnet: 192.168.17.0\/24\r\n          gateway: 192.168.17.1\r\n\r\nvolumes:\r\n  my_pihole:\r\n  my_dnsmasq:\r\n\r\nservices:\r\n  pihole:\r\n    container_name: my_pihole\r\n    image: pihole\/pihole:latest\r\n    networks: \r\n      my_macvlan_network:\r\n        ipv4_address: 192.168.17.22\r\n    volumes:\r\n      - my_pihole:\/etc\/pihole\/\r\n      - my_dnsmasq:\/etc\/dnsmasq.d\/\r\n    environment:\r\n      TZ: 'Europe\/London'\r\n      # WEBPASSWORD: 'set a secure password here or it will be random'\r\n    dns:\r\n      - 127.0.0.1\r\n      - 1.1.1.1\r\n    # Recommended but not required (DHCP needs NET_ADMIN)\r\n    #   https:\/\/github.com\/pi-hole\/docker-pi-hole#note-on-capabilities\r\n    cap_add:\r\n      - NET_ADMIN\r\n    restart: unless-stopped<\/pre>\n
This works … sort of. For one docker compose irritatingly prepends my directory name to all the networks and volumes it creates and that seems to be intentional with no way to bypass via the CLI or YAML file (see this<\/a> forum post for a discussion if interested). \u00a0And for another setting this up via YAML takes longer and outputs some errors like the DNS server not being set correctly (the above syntax is correct, so not sure what the deal is) … overall the docker run way of doing things seemed cleaner and more intuitive to using docker compose. So I left it.\u00a0<\/p>\n
The prefix thing can be fixed for volumes at least by adding a name<\/code> parameter<\/a> apparently, but that only works for volumes & not networks, and to use that I’ll have to switch to version 3.4 of the YAML file but that breaks the macvlan definition as IPAM config for it is only supported in version 2<\/a>. Eugh!<\/p>\n
All of this kind of brings me to a rant about this new “infrastructure as code” way of configuring things via YAML and JSON not just with Docker but also using tools like ARM templates, Terraform etc. At the risk of sounding like a luddite I am just not a fan of them! I am not averse to scripting or writing commands with arcane switches, and I’ll happily write a series of commands to create a new network and deploy a VM in Azure for instance (similar to what I did with the docker run<\/code> commands earlier) … that is intuitive to me and makes sense, I feel for it … but putting the same info into a JSON file and then using ARM templates or Terraform just seems an extra overhead and doesn’t work well with my way of thinking. I have spent time with ARM templates, so this is not me saying something without making an effort … I’ve made the effort, written some templates too and read a bit on the syntax etc., but I just hate it in the end. I get the idea behind using a template file, and I understand “infrastructure as code” but it just doesn’t compute in my head. I’d rather deploy stuff via a series of CLI commands than spend the time learning JSON or YAML or Terraform syntax and then using that tool set to deploy stuff (oh and not to mention keeping track of API versions for the templates like with the docker compose file above where different versions have different features). If I want to do coding I’d have become a developer, not become a sys admin!<\/p>\n
Anyways, end of rant. :)<\/p>\n","protected":false},"excerpt":{"rendered":"
This post isn’t much about Pi-Hole, sorry for the misleading title. It is a continuation to my previous post though and I couldn’t think of any other title.\u00a0 I thought I’d put the docker commands of the previous post into a docker compose YAML file as that seems to be the fashion. Here’s what I … Continue reading Pi-Hole Docker (contd.)<\/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":[888,498],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/4743"}],"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=4743"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/4743\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=4743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=4743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=4743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}