<?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>Ubuntu on My Mini Maker Space!</title>
    <link>https://my.minimaker.space/categories/ubuntu/</link>
    <description>Recent content in Ubuntu 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/ubuntu/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>
  </channel>
</rss>
