Footloose not working on WSL?

[jwillmer]

I installed footloose on WSL (Windows Subsystem for Linux) following the readme:

curl -Lo footloose https://github.com/weaveworks/footloose/releases/download/0.6.4/footloose-0.6.4-linux-x86_64
chmod +x footloose
sudo mv footloose /usr/local/bin/

But I can't run it:

$ footloose
/usr/local/bin/footloose: line 1: Not: command not found

$ footloose --help
/usr/local/bin/footloose: line 1: Not: command not found

[stelb]

Your download failed, as the link returns 404..
And your footloose is a textfile interpreted as shellscript and not a binary.
See e.g. docker/compose#6268

[jwillmer]

Oh, O.K., I did not notice that. Maybe someone should update the readme with a working link. Thank you!

[jwillmer]

I managed to download the correct footlose binary but running the image does not work:

$ footloose config create --replicas 3
$ footloose create
INFO[0000] Creating SSH key: cluster-key ...
INFO[0000] Pulling image: quay.io/footloose/centos7:0.6.3 ...
INFO[0020] Creating machine: cluster-node0 ...
INFO[0024] Creating machine: cluster-node1 ...
INFO[0026] Creating machine: cluster-node2 ...

$ docker ps
CONTAINER ID   IMAGE                             COMMAND        CREATED         STATUS         PORTS                   NAMES
8bca3e514a00   quay.io/footloose/centos7:0.6.3   "/sbin/init"   3 seconds ago   Up 2 seconds   0.0.0.0:52943->22/tcp   cluster-node2
7344014663fa   quay.io/footloose/centos7:0.6.3   "/sbin/init"   5 seconds ago   Up 4 seconds   0.0.0.0:52942->22/tcp   cluster-node1
a022131323f7   quay.io/footloose/centos7:0.6.3   "/sbin/init"   7 seconds ago   Up 5 seconds   0.0.0.0:52941->22/tcp   cluster-node0

$ docker logs 8bca3e514a00
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems, freezing.

[stelb]

Probably this: microsoft/WSL#4189

[marzelin]

You need SystemD but WSL2 doesn't have SystemD running as an init process like typical distributions (and it's hard to start it because it requires PID 1) but there's a workaround:

# Install the required packages for SystemD
apt install -yqq fontconfig daemonize

# Create the starting script for SystemD
vi /etc/profile.d/00-wsl2-systemd.sh
SYSTEMD_PID=$(ps -ef | grep '/lib/systemd/systemd --system-unit=basic.target$' | grep -v unshare | awk '{print $2}')

if [ -z "$SYSTEMD_PID" ]; then
   sudo /usr/bin/daemonize /usr/bin/unshare --fork --pid --mount-proc /lib/systemd/systemd --system-unit=basic.target
   SYSTEMD_PID=$(ps -ef | grep '/lib/systemd/systemd --system-unit=basic.target$' | grep -v unshare | awk '{print $2}')
fi

if [ -n "$SYSTEMD_PID" ] && [ "$SYSTEMD_PID" != "1" ]; then
    exec sudo /usr/bin/nsenter -t $SYSTEMD_PID -a su - $LOGNAME
fi

Terminate wsl from powershell:

wsl --shutdown

After this /sys/fs/cgroup/systemd should be able to be mounted and you should get your vms running.