<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unraid on StackNotes</title><link>https://stacknotes.co.uk/categories/unraid/</link><description>Recent content in Unraid on StackNotes</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Sat, 07 Nov 2026 12:10:00 +0000</lastBuildDate><atom:link href="https://stacknotes.co.uk/categories/unraid/index.xml" rel="self" type="application/rss+xml"/><item><title>Unraid Docker service failed to start: the line that names your cause</title><link>https://stacknotes.co.uk/articles/unraid-docker-service-failed-to-start/</link><pubDate>Sat, 07 Nov 2026 12:10:00 +0000</pubDate><guid>https://stacknotes.co.uk/articles/unraid-docker-service-failed-to-start/</guid><description>&lt;p&gt;&lt;em&gt;The short version: &amp;ldquo;Docker service failed to start&amp;rdquo; means dockerd exited, and it says why on the way out. One line, in its own log. Find that line, match it to one of the seven cases below, and you know whether to grow the image, rebuild it, or fix a file. Deleting the image is the fourth thing to try, not the first.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;I am writing this from inside a container on an Unraid box, which is an odd place to sit while writing about Docker refusing to start. The filesystem under my feet is a btrfs subvolume inside &lt;code&gt;/mnt/cache/system/docker/docker.img&lt;/code&gt;, a 150 GB image on &lt;code&gt;/dev/loop2&lt;/code&gt; with 31 GB used. When that image has a bad day, my root filesystem goes with it.&lt;/p&gt;</description></item></channel></rss>