<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on My Mini Maker Space!</title>
    <link>https://my.minimaker.space/categories/docker/</link>
    <description>Recent content in Docker on My Mini Maker Space!</description>
    <generator>Hugo -- 0.127.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Oct 2024 14:45:39 +1300</lastBuildDate>
    <atom:link href="https://my.minimaker.space/categories/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop and Disable systemd-resolved</title>
      <link>https://my.minimaker.space/2024/10/27/stop-and-disable-systemd-resolved/</link>
      <pubDate>Sun, 27 Oct 2024 14:45:39 +1300</pubDate>
      <guid>https://my.minimaker.space/2024/10/27/stop-and-disable-systemd-resolved/</guid>
      <description>When I build a Pi-Hole server I usually install it in Docker on an Ubuntu Server on an old Raspberry Pi or Intel NUC.
The default install of Ubuntu has systemd-resolved installed which clashes when you bring the Pi-hole Docker container up.
I can never remember the steps to disable systemd-resolved so this is my reminder :-)
Stop and Disable systemd-resolved Check the Status of systemd-resolved: First, check if systemd-resolved is running:</description>
    </item>
    <item>
      <title>Pi-hole in a Docker Container on a Raspberry Pi</title>
      <link>https://my.minimaker.space/2018/04/23/pi-hole-in-a-docker-container-on-a-raspberry-pi/</link>
      <pubDate>Mon, 23 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2018/04/23/pi-hole-in-a-docker-container-on-a-raspberry-pi/</guid>
      <description>Logos Property of Pi-hole &amp;amp; Docker.
While I was disappearing down a rabbit hole investigating unbound as a DNS Privacy server, I came across Pi-hole – A black hole for Internet advertisements.
I’ve always used uBlock Origin for ad blocking but that is a per client thing which is a bit of a hassle.
Pi-hole provides ad blocking for all clients on the network, seamlessly. I just configure DNS on each client, via DHCP, to point towards the Pi-Hole server.</description>
    </item>
    <item>
      <title>Raspberry Pi Docker Container to send all LAN DNS requests to Cloudflare’s 1.1.1.1 DNS over TLS</title>
      <link>https://my.minimaker.space/2018/04/21/raspberry-pi-docker-container-to-send-all-lan-dns-requests-to-cloudflares-1.1.1.1-dns-over-tls/</link>
      <pubDate>Sat, 21 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2018/04/21/raspberry-pi-docker-container-to-send-all-lan-dns-requests-to-cloudflares-1.1.1.1-dns-over-tls/</guid>
      <description>I wanted to implement this on a Raspberry Pi that I have running Docker. However, I wasn’t able to find an image in Docker Hub for the ARM architecture that the Raspberry Pi uses so I made my own based on the x86-64 image, here.
Place the Dockerfile and unbound.conf in the same directory. Docker file: FROM arm32v6/alpine:3.7 EXPOSE 53/udp RUN apk add --update --no-cache -q --progress unbound &amp;amp;&amp;amp; \ rm -rf /etc/unbound/unbound.</description>
    </item>
    <item>
      <title>Deploy Portainer in a Docker Container</title>
      <link>https://my.minimaker.space/2018/03/05/deploy-portainer-in-a-docker-container/</link>
      <pubDate>Mon, 05 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2018/03/05/deploy-portainer-in-a-docker-container/</guid>
      <description>Portainer is an Open-Source lightweight Management UI which allows you to easily manage your Docker Hosts or Swarm Clusters
Port 9000 of the container is published to the host A 16 megabyte limit is set on the container, in this instance. Data is persisted in a named volume called ‘portainer_data’ docker run -d \ --name portainer \ --restart=unless-stopped \ --memory=16m \ -p 9000:9000 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v portainer_data:/data \ portainer/portainer The container can also be deployed using the more explicit –mount flag which became available for standalone containers in Docker 17.</description>
    </item>
    <item>
      <title>Deploy Watchtower in a Docker Container</title>
      <link>https://my.minimaker.space/2018/03/05/deploy-watchtower-in-a-docker-container/</link>
      <pubDate>Mon, 05 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2018/03/05/deploy-watchtower-in-a-docker-container/</guid>
      <description>Watchtower is an application that will monitor your running Docker containers and watch for changes to the images that those containers were originally started from. If watchtower detects that an image has changed, it will automatically restart the container using the new image.
A 16 megabyte limit is set on the container, in this instance. I’ve added a hostname for this container because Watchtower sends emails with the hostname of the Watchtower Docker container in the subject line.</description>
    </item>
    <item>
      <title>Install Docker and Compose on Ubuntu 16.04 LTS</title>
      <link>https://my.minimaker.space/2018/03/05/install-docker-and-compose-on-ubuntu-16.04-lts/</link>
      <pubDate>Mon, 05 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2018/03/05/install-docker-and-compose-on-ubuntu-16.04-lts/</guid>
      <description>#!/bin/bash apt-get update apt-get install \ apt-transport-https \ ca-certificates \ curl \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - add-apt-repository \ &amp;#34;deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable&amp;#34; apt-get update apt-get install -y \ docker-ce \ docker-compose If you plan on using the –memory flag when creating containers, you may need to enable memory and swap accounting in the Kernel.
Log into the Ubuntu host as a user with sudo privileges.</description>
    </item>
    <item>
      <title>Install Docker and Compose on Debian 9 Stretch</title>
      <link>https://my.minimaker.space/2017/10/03/install-docker-and-compose-on-debian-9-stretch/</link>
      <pubDate>Tue, 03 Oct 2017 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2017/10/03/install-docker-and-compose-on-debian-9-stretch/</guid>
      <description>#!/bin/bash apt-get update apt-get install -y \ apt-transport-https \ ca-certificates \ curl \ gnupg2 \ software-properties-common curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add - add-apt-repository \ &amp;#34;deb [arch=amd64] https://download.docker.com/linux/debian \ $(lsb_release -cs) \ stable&amp;#34; apt-get update apt-get install -y \ docker-ce \ docker-compose If you plan on using the –memory flag when creating containers, you may need to enable memory and swap accounting in the Kernel.
Log into the Ubuntu host as a user with sudo privileges.</description>
    </item>
    <item>
      <title>Check or Change the Timezone in Debian</title>
      <link>https://my.minimaker.space/2017/08/09/check-or-change-the-timezone-in-debian/</link>
      <pubDate>Wed, 09 Aug 2017 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2017/08/09/check-or-change-the-timezone-in-debian/</guid>
      <description>To see or change what timezone your Debian system is configured for:
dpkg-reconfigure tzdata More detailed information is available in the Debian Wiki
More specifically, I used this in a setup of HypriotOS, a minimal Debian-based operating systems that is optimised to run Docker on ARM devices. In this instance it was an old Raspberry Pi Model B running NodeRed in a Docker Container.
I needed to get the time in the Docker Container to match the time on the host.</description>
    </item>
    <item>
      <title>Show Docker Stats with Container Name Instead of Container ID</title>
      <link>https://my.minimaker.space/2017/01/14/show-docker-stats-with-container-name-instead-of-container-id/</link>
      <pubDate>Sat, 14 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2017/01/14/show-docker-stats-with-container-name-instead-of-container-id/</guid>
      <description>docker stats $(docker ps --format={{.Names}}) More details in the Docker CLI Reference</description>
    </item>
    <item>
      <title>Run a Bash Shell in a Running Docker Container</title>
      <link>https://my.minimaker.space/2016/11/24/run-a-bash-shell-in-a-running-docker-container/</link>
      <pubDate>Thu, 24 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2016/11/24/run-a-bash-shell-in-a-running-docker-container/</guid>
      <description>There was a time when I could never remember this&amp;hellip; but now I&amp;rsquo;ve typed it so often!
docker exec -it container_name /bin/bash More details in the Docker CLI Reference</description>
    </item>
    <item>
      <title>Docker - Logs</title>
      <link>https://my.minimaker.space/2016/11/06/docker-logs/</link>
      <pubDate>Sun, 06 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2016/11/06/docker-logs/</guid>
      <description>Fetch and follow the log output of a Docker container:
docker logs -f CONTAINER_NAME </description>
    </item>
    <item>
      <title>Docker - Managing Dangling Volumes</title>
      <link>https://my.minimaker.space/2016/09/22/docker-managing-dangling-volumes/</link>
      <pubDate>Thu, 22 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://my.minimaker.space/2016/09/22/docker-managing-dangling-volumes/</guid>
      <description>List Dangling Volumes docker volume ls -qf dangling=true Remove Dangling Volumes docker volume rm $(docker volume ls -qf dangling=true) </description>
    </item>
  </channel>
</rss>
