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
Leash fails to start on Docker Desktop: xt_cgroup module unavailable in LinuxKit #60
Kia ora team. Starting about a week ago, I noticed that when I run leash on my Mac with Docker Desktop, the leash container crashes shortly after startup with the following error in its logs:
leash: FATAL: could not apply cgroup-based control plane isolation
leash: This security control is required to prevent target container from accessing leashd API
{timestamp} exit status 1
The xt_cgroup kernel module isn't available in Docker Desktop's LinuxKit VM (6.12.68-linuxkit), causing the cgroup-based iptables rule to fail with "RULE_APPEND failed (Invalid argument)".
Workaround
I did some experimentation, and if I switch to the jay/secrets branch (commit b35fd2c), there appears to be a fix for the issue (changes the FATAL to a WARNING and uses loopback-only blocking as a fallback).
I rebuilt the containers on this branch, and the problem goes away—so it seems like this issue is already on the team's radar. Just wanted to flag it as it impacts the latest published Docker images in AWS.
I am getting the same error. Running Manjaro with Docker daemon (no Docker Desktop).
iptables v1.8.9 (nf_tables): RULE_APPEND failed (Invalid argument): rule in chain OUTPUT
leash: FATAL: could not apply cgroup-based control plane isolation
leash: This security control is required to prevent target container from accessing leashd API
Jay's fix in that commit is incomplete because no actual loopback-only blocking is implemented. The target has unrestricted access to the leashd API on port 18080.
We will need to go back to the drawing board for this.
Activity
gaganpreet commentedon Feb 22, 2026
I am getting the same error. Running Manjaro with Docker daemon (no Docker Desktop).
CC starts in leash but there's no network access.
navanchauhan commentedon Mar 4, 2026
Investigating. I haven't been able to recreate it yet on my machine.
Edit: Reproduced the issue on the latest version of Docker Desktop
navanchauhan commentedon Mar 4, 2026
Jay's fix in that commit is incomplete because no actual loopback-only blocking is implemented. The target has unrestricted access to the leashd API on port 18080.
We will need to go back to the drawing board for this.
network: fall back to blanket port block when cgroup isolation unavai…
network: fall back to blanket port block when cgroup isolation unavai…