You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b89968f
Browse filesBrowse the repository at this point in the historyBrowse files
<p><strong>Checking a limit yourself:</strong> run <code>droidspaces -n <name> info</code> on the host, or <code>cat /proc/meminfo</code> inside the container.</p>
351
352
<p>There is no fix for this at the moment. Intercepting <code>sysinfo()</code> needs seccomp user notifications, which only exist on kernel 5.0 and later.</p>
352
353
<hr/>
354
+
<p><aid="controller-disabled-at-boot"></a></p>
355
+
<h2id="a-resource-limit-is-unavailable-although-its-kernel-option-is-enabled">A resource limit is unavailable although its kernel option is enabled <aclass="header-anchor" href="#a-resource-limit-is-unavailable-although-its-kernel-option-is-enabled">#</a></h2>
356
+
<p><strong>Symptom:</strong><code>droidspaces check</code> marks "Memory limit support", "CPU limit support" or "Process limit support" as missing, the app greys out the matching toggle, or a start prints for example <code>memory.max is not available on this kernel</code>, yet <code>/proc/config.gz</code> has the option (<code>CONFIG_MEMCG=y</code>, <code>CONFIG_CFS_BANDWIDTH=y</code>, <code>CONFIG_CGROUP_PIDS=y</code>).</p>
357
+
<p><strong>Cause:</strong> the controller is built in but was switched off at boot. Look at the last column of <code>/proc/cgroups</code>:</p>
<p>A <code>0</code> there means the kernel was booted with <code>cgroup_disable=</code> for that controller: <code>cgroup_disable=memory</code>, <code>cgroup_disable=cpu</code> or <code>cgroup_disable=pids</code>. Confirm it with <code>cat /proc/cmdline</code>. <code>cgroup_disable=memory</code> is the common one, many vendor and custom Android kernels use it to save a little memory.</p>
362
+
<p><strong>Fix:</strong> remove the argument from the kernel command line. It comes from <code>CONFIG_CMDLINE</code> in the kernel config, from the boot image header (<code>boot</code> or <code>vendor_boot</code>), or from the bootloader. If <code>zcat /proc/config.gz | grep CMDLINE</code> does not show it, it is one of the last two. Avoid <code>CONFIG_CMDLINE_FORCE</code> as a way out on Android: it drops every other argument the device passes at boot as well.</p>
363
+
<p>The container still starts either way, only the limit is skipped.</p>
364
+
<hr/>
353
365
<h2id="getting-help">Getting help <aclass="header-anchor" href="#getting-help">#</a></h2>
354
366
<p>If your problem is not listed here:</p>
355
367
<ol>
@@ -365,7 +377,7 @@ <h2 id="getting-help">Getting help <a class="header-anchor" href="#getting-help"
365
377
<navclass="doc-nav" aria-label="Pages"><ahref="cool-things-you-can-do.html" class="doc-nav-prev"><small>Previous</small>Cool things you can do</a><ahref="community-supported-devices.html" class="doc-nav-next"><small>Next</small>Community-supported devices</a></nav>
366
378
</main>
367
379
<asideclass="toc-column">
368
-
<navclass="toc" aria-label="On this page"><pclass="toc-title">On this page</p><ul><liclass="toc-h3"><ahref="#quick-navigation">Quick navigation</a></li><liclass="toc-h2"><ahref="#modern-distros-arch-fedora-etc-failure-on-legacy-kernels">Modern distros (Arch, Fedora, etc.) failure on legacy kernels</a></li><liclass="toc-h2"><ahref="#required-key-not-available">"Required key not available"</a></li><liclass="toc-h2"><ahref="#mount-errors-on-kernel-414">Mount errors on kernel 4.14</a></li><liclass="toc-h2"><ahref="#overlayfs-not-supported-f2fs">OverlayFS not supported (f2fs)</a></li><liclass="toc-h2"><ahref="#container-name-conflicts">Container name conflicts</a></li><liclass="toc-h2"><ahref="#systemd-hangs-on-older-kernels">systemd hangs on older kernels</a></li><liclass="toc-h2"><ahref="#container-wont-stop">Container won't stop</a></li><liclass="toc-h2"><ahref="#rootfs-image-io-errors-on-android">Rootfs image I/O errors on Android</a></li><liclass="toc-h2"><ahref="#networking-is-completely-dead---ping-fails-with-socket-permission-denied">Networking is completely dead - ping fails with "socket: permission denied"</a></li><liclass="toc-h2"><ahref="#dns--name-resolution-issues">DNS / name resolution issues</a></li><liclass="toc-h2"><ahref="#wifimobile-data-disconnects">WiFi/mobile data disconnects</a></li><liclass="toc-h2"><ahref="#selinux-induced-rootfs-corruption-directory-mode">SELinux-induced rootfs corruption (directory mode)</a></li><liclass="toc-h2"><ahref="#reclaiming-storage-sparse-image">Reclaiming storage (sparse image)</a></li><liclass="toc-h2"><ahref="#wi-fi-power-save-on-causing-sluggish-networking-on-android">Wi-Fi Power save: on causing sluggish networking on Android</a></li><liclass="toc-h3"><ahref="#1-install-required-utilities">1. Install required utilities</a></li><liclass="toc-h3"><ahref="#2-create-the-watchdog-script">2. Create the watchdog script</a></li><liclass="toc-h3"><ahref="#3-wire-up-the-init-service">3. Wire up the init service</a></li><liclass="toc-h2"><ahref="#luci-or-another-tool-shows-the-hosts-ram-and-load-despite-a-limit">LuCI, or another tool, shows the host's RAM and load despite a limit</a></li><liclass="toc-h2"><ahref="#getting-help">Getting help</a></li></ul></nav>
380
+
<navclass="toc" aria-label="On this page"><pclass="toc-title">On this page</p><ul><liclass="toc-h3"><ahref="#quick-navigation">Quick navigation</a></li><liclass="toc-h2"><ahref="#modern-distros-arch-fedora-etc-failure-on-legacy-kernels">Modern distros (Arch, Fedora, etc.) failure on legacy kernels</a></li><liclass="toc-h2"><ahref="#required-key-not-available">"Required key not available"</a></li><liclass="toc-h2"><ahref="#mount-errors-on-kernel-414">Mount errors on kernel 4.14</a></li><liclass="toc-h2"><ahref="#overlayfs-not-supported-f2fs">OverlayFS not supported (f2fs)</a></li><liclass="toc-h2"><ahref="#container-name-conflicts">Container name conflicts</a></li><liclass="toc-h2"><ahref="#systemd-hangs-on-older-kernels">systemd hangs on older kernels</a></li><liclass="toc-h2"><ahref="#container-wont-stop">Container won't stop</a></li><liclass="toc-h2"><ahref="#rootfs-image-io-errors-on-android">Rootfs image I/O errors on Android</a></li><liclass="toc-h2"><ahref="#networking-is-completely-dead---ping-fails-with-socket-permission-denied">Networking is completely dead - ping fails with "socket: permission denied"</a></li><liclass="toc-h2"><ahref="#dns--name-resolution-issues">DNS / name resolution issues</a></li><liclass="toc-h2"><ahref="#wifimobile-data-disconnects">WiFi/mobile data disconnects</a></li><liclass="toc-h2"><ahref="#selinux-induced-rootfs-corruption-directory-mode">SELinux-induced rootfs corruption (directory mode)</a></li><liclass="toc-h2"><ahref="#reclaiming-storage-sparse-image">Reclaiming storage (sparse image)</a></li><liclass="toc-h2"><ahref="#wi-fi-power-save-on-causing-sluggish-networking-on-android">Wi-Fi Power save: on causing sluggish networking on Android</a></li><liclass="toc-h3"><ahref="#1-install-required-utilities">1. Install required utilities</a></li><liclass="toc-h3"><ahref="#2-create-the-watchdog-script">2. Create the watchdog script</a></li><liclass="toc-h3"><ahref="#3-wire-up-the-init-service">3. Wire up the init service</a></li><liclass="toc-h2"><ahref="#luci-or-another-tool-shows-the-hosts-ram-and-load-despite-a-limit">LuCI, or another tool, shows the host's RAM and load despite a limit</a></li><liclass="toc-h2"><ahref="#a-resource-limit-is-unavailable-although-its-kernel-option-is-enabled">A resource limit is unavailable although its kernel option is enabled</a></li><liclass="toc-h2"><ahref="#getting-help">Getting help</a></li></ul></nav>
0 commit comments