<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=7969&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7969</link>
		<description><![CDATA[The most recent posts in [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys.]]></description>
		<lastBuildDate>Fri, 05 Jun 2026 16:37:41 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64168#p64168</link>
			<description><![CDATA[<p>@yaser</p><p>Once you’ve run my script, you should already have a fully functional Docker installation. Why are you then doing something that breaks it? Or are you still experiencing the same cgroups issues after running my script?</p><p>&#160; &#160; -- mr-addams</p>]]></description>
			<author><![CDATA[dummy@example.com (mr-addams)]]></author>
			<pubDate>Fri, 05 Jun 2026 16:37:41 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64168#p64168</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64124#p64124</link>
			<description><![CDATA[<p>I can confirm using @mr-addams &#039;s script to install docker on devuan 6 with standard sysv init system works perfect.<br />I didn&#039;t find out a way around my problem with <em>cgroups</em> but following <a href="https://dev1galaxy.org/viewtopic.php?id=6576" rel="nofollow">this guide</a> recreates the issue.</p>]]></description>
			<author><![CDATA[dummy@example.com (yaser)]]></author>
			<pubDate>Wed, 03 Jun 2026 23:31:20 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64124#p64124</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64044#p64044</link>
			<description><![CDATA[<p>@yaser</p><p>Thanks for the report! This was fixed today. The issue was that lsb_release -cs on Devuan returns excalibur, but Docker&#039;s repository only uses Debian codenames (bookworm). <br />The fix adds a mapping: excalibur → bookworm, daedalus → bullseye, etc. Pull the latest version of the script and it should work now.</p><p>&#160; &#160; — mr-addams</p>]]></description>
			<author><![CDATA[dummy@example.com (mr-addams)]]></author>
			<pubDate>Sat, 30 May 2026 11:47:34 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64044#p64044</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64026#p64026</link>
			<description><![CDATA[<p>Thanks @mark0x01 and @mr-addams</p><p>i tried to install docker with updated script (thanks for providing this tho). there is a bug i guess:</p><div class="codebox"><pre><code>6. Adding Docker repository...
Hit:1 http://deb.devuan.org/merged excalibur InRelease
Hit:2 http://deb.devuan.org/merged excalibur-security InRelease
Ign:3 https://download.docker.com/linux/debian excalibur InRelease
Hit:4 http://deb.devuan.org/merged excalibur-updates InRelease
Hit:5 http://deb.devuan.org/merged excalibur-backports InRelease
Err:6 https://download.docker.com/linux/debian excalibur Release
  404  Not Found [IP: 108.138.7.88 443]
Reading package lists... Done
E: The repository &#039;https://download.docker.com/linux/debian excalibur Release&#039; does not have a Release file.
N: Updating from such a repository can&#039;t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (yaser)]]></author>
			<pubDate>Thu, 28 May 2026 15:37:49 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64026#p64026</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64008#p64008</link>
			<description><![CDATA[<p>You are welcome.</p><p>Nice to be able to contribute a little back while the old brain is still functioning.</p>]]></description>
			<author><![CDATA[dummy@example.com (mark0x01)]]></author>
			<pubDate>Wed, 27 May 2026 05:43:51 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64008#p64008</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64003#p64003</link>
			<description><![CDATA[<p>@yaser — regarding your original issue with fsconfig and cgroup errors on Devuan: the script uses overlay2 + cgroupfs in daemon.json, which avoids the cgroup v2 problems. Try the updated version below.&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; </p><p>@mark0x01 — thanks for the thorough bug report! Here&#039;s the breakdown:&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;</p><p> Root cause: Two bugs in the script:&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;</p><p>1. Init script (line 109) had /usr/bin/dockerd hardcoded, but on Devuan the binary is at /usr/sbin/dockerd (Debian Policy requires system daemons in sbin/; Docker Inc puts them in bin/).<br />2. Error message (line 5) said docker-full-install.sh instead of antix-docker-install.sh.&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;</p><p>What changed:&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;<br />- The init script (/etc/init.d/docker) now auto-detects dockerd via command -v → /usr/bin/dockerd → /usr/sbin/dockerd. This detection runs after Docker is already installed (step 11 in the script), so if dockerd is missing at that point — something really went wrong during install, and exit 1 is intentional for fail-fast diagnostics.&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; <br />- Main script also uses pkill -f dockerd (no hardcoded path) for pre-install cleanup.<br />- Error message corrected to antix-docker-install.sh.<br />- Removed docker-model-plugin from default install (bloat for low-resource distros).&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; <br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; <br />Updated script:</p><p>wget <a href="https://raw.githubusercontent.com/mr-addams/antix-docker-install/main/antix-docker-install.sh" rel="nofollow">https://raw.githubusercontent.com/mr-ad … install.sh</a>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; </p><p>Now works on antiX, Devuan, MX Linux and any Debian fork with sysVinit.</p><p>Thanks again — both bugs fixed upstream!</p><p>&#160; &#160; &#160;— mr-addams</p>]]></description>
			<author><![CDATA[dummy@example.com (mr-addams)]]></author>
			<pubDate>Tue, 26 May 2026 23:38:35 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64003#p64003</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63883#p63883</link>
			<description><![CDATA[<p>Encountered the same and then more problems, and even more after rebooting.</p><p>I used antix-docker-install.sh script to clean up and reinstall docker successfully, once I fixed a bug in it.</p><p><a href="https://github.com/mr-addams/antix-docker-install" rel="nofollow">https://github.com/mr-addams/antix-docker-install</a></p><p>It has a bug, and non critical error.</p><p>In the script, change line 109 DOCKERD=/usr/bin/dockerd to DOCKERD=/usr/sbin/dockerd</p><p>and line 5 has the wrong script name.&#160; &#160; &#160;echo &quot;Run as root: sudo bash docker-full-install.sh&quot;&#160; should be antix-docker-install.sh</p>]]></description>
			<author><![CDATA[dummy@example.com (mark0x01)]]></author>
			<pubDate>Mon, 18 May 2026 02:56:54 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63883#p63883</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] Docker: fsconfig fails and cgroup says unknown subsys]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63767#p63767</link>
			<description><![CDATA[<p>Hi,</p><p>newbie here!</p><p>I just installed docker.io on Devuan 6 sysvinit. doing <em>sudo service docker restart</em> gives:</p><div class="codebox"><pre><code>Stopping Docker: docker.
mount: /sys/fs/cgroup/cpuset: fsconfig() failed: cgroup: Unknown subsys name &#039;cpuset&#039;.
       dmesg(1) may have more information after failed mount system call.
mount: /sys/fs/cgroup/memory: fsconfig() failed: cgroup: Unknown subsys name &#039;memory&#039;.
       dmesg(1) may have more information after failed mount system call.
Starting Docker: docker.</code></pre></div><p>What step i missed? what version of cgroups&#160; we are using?</p>]]></description>
			<author><![CDATA[dummy@example.com (yaser)]]></author>
			<pubDate>Tue, 12 May 2026 05:45:29 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63767#p63767</guid>
		</item>
	</channel>
</rss>
