Revision history [back]

Starting containers on the Jolla would be an awesome feature.

Please enable the necessary namespace features CONFIG_UTS_NS, CONFIG_IPC_NS, CONFIG_PID_NS, and CONFIG_NET_NS in the Jolla kernel. This would enable systemd-nspawn to start containers.

Currently when I try to use systemd-nspawn I get:

[root@Jolla containers]# systemd-nspawn --read-only -bD Fedora-Minimal-armhfp-21_Beta-4-sda
The kernel auditing subsystem is known to be incompatible with containers.
Please make sure to turn off auditing with 'audit=0' on the kernel command
line before using systemd-nspawn. Sleeping for 5s...
Spawning namespace container on /media/sdcard/a1471002-ecc9-4bed-9beb-a5092113fe1f/data/containers/Fedora-Minimal-armhfp-21_Beta-4-sda (console is /dev/pts/4).
clone() failed, do you have namespace support enabled in your kernel? (You need UTS, IPC, PID and NET namespacing built in): Invalid argument

Being able to start containers on the Jolla phone would enable users to run many popular Linux distributions w/o actually installing those. Many distributions provide disk images for ARM which can be started as containers.

Starting containers on the Jolla would be an awesome feature.

Please enable the necessary namespace features CONFIG_UTS_NS, CONFIG_IPC_NS, CONFIG_PID_NS, and CONFIG_NET_NS in the Jolla kernel. This would enable systemd-nspawn to start containers.

Currently when I try to use systemd-nspawn I get:

[root@Jolla containers]# systemd-nspawn --read-only -bD Fedora-Minimal-armhfp-21_Beta-4-sda
The kernel auditing subsystem is known to be incompatible with containers.
Please make sure to turn off auditing with 'audit=0' on the kernel command
line before using systemd-nspawn. Sleeping for 5s...
Spawning namespace container on /media/sdcard/a1471002-ecc9-4bed-9beb-a5092113fe1f/data/containers/Fedora-Minimal-armhfp-21_Beta-4-sda (console is /dev/pts/4).
clone() failed, do you have namespace support enabled in your kernel? (You need UTS, IPC, PID and NET namespacing built in): Invalid argument

Being able to start containers on the Jolla phone would enable users to run many popular Linux distributions w/o actually installing those. Many distributions provide disk images for ARM which can be started as containers.

Starting containers on the Jolla would be an awesome feature.

Please enable the necessary namespace features CONFIG_UTS_NS, CONFIG_IPC_NS, CONFIG_PID_NS, and CONFIG_NET_NS in the Jolla kernel. This would enable systemd-nspawn to start containers.

Currently when I try to use systemd-nspawn I get:

[root@Jolla containers]# systemd-nspawn --read-only -bD Fedora-Minimal-armhfp-21_Beta-4-sda
The kernel auditing subsystem is known to be incompatible with containers.
Please make sure to turn off auditing with 'audit=0' on the kernel command
line before using systemd-nspawn. Sleeping for 5s...
Spawning namespace container on /media/sdcard/a1471002-ecc9-4bed-9beb-a5092113fe1f/data/containers/Fedora-Minimal-armhfp-21_Beta-4-sda (console is /dev/pts/4).
clone() failed, do you have namespace support enabled in your kernel? (You need UTS, IPC, PID and NET namespacing built in): Invalid argument

Being able to start containers on the Jolla phone would enable users to run many popular Linux distributions w/o actually installing those. Many distributions provide disk images for ARM which can be started as containers.

Update: @anandrkris recommended I bring this request to the sailfish-devel mailing list. Here's the link to the mailing list thread: https://lists.sailfishos.org/pipermail/devel/2014-December/005371.html