Solutions when Termux proot cannot use the systemctl command

infoivonblog.nkfjt@aleeas.com (Ivon Huang) — Sat, 31 Aug 2024 23:00:00 +0800

Systemd is an init program. Almost all Linux distributions use Systemd to manage system services, and common commands include systemctl, journalctl, and so on.

However, Termux cannot use Systemd. If you run commands related to systemctl start inside a Termux proot-distro or chroot container environment, you will see this error: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

This is because the container environment does not support Systemd.

There is actually no real solution, unless the Termux development team learns from Microsoft WSL and finds a way to make Systemd run. However, we do have some alternatives to address this problem.

Method 1: Start the program directly from the executable path
#

First, understand that Systemd is just an init program for managing system services. It is responsible for starting programs after Linux boots and letting users turn programs on and off. But simply starting a program does not actually require systemctl.

For example, to start the SSH service in proot Debian, the Systemd way is to run the following command:

sudo systemctl start sshd

If we find Systemd’s service file /etc/systemd/system/sshd.service (most Systemd service files are here), we will see that what follows ExecStart= is the command it really executes:

[Service]
EnvironmentFile=-/etc/default/ssh
ExecStartPre=/usr/sbin/sshd -t
ExecStart=/usr/sbin/sshd -D

Therefore, the SSH service can be started directly with this command and run in the background:

mkdir -p /run/sshd

/usr/sbin/sshd -D

Note: programs inside Termux proot-distro cannot use ports below 1000. When logging in to proot-distro, add the --fix-low-ports parameter to redirect SSH port 22 to 2022.

If you want to automatically start a specific program after logging in to proot-distro, the simplest way is to add the command you want to run to ~/.bashrc in the user’s home directory.

Method 2: Switch to a distribution that uses OpenRC
#

OpenRC and runit are more traditional init programs. They are not as complex as Systemd, and they can run and manage services in proot. Users unfamiliar with OpenRC commands can refer to the Systemd and OpenRC command comparison table below.

At present, the proot-distro distribution that uses OpenRC is Alpine Linux, while Artix Linux and Void Linux use runit.

Install Alpine Linux

proot-distro install alpine
proot-distro login alpine

Install the OpenRC package

apk add openrc

After that, append this command when logging in to proot, and the OpenRC program will start

proot-distro login alpine --fix-low-ports -- /bin/ash -c "/sbin/openrc default; /bin/ash -l"

After that, you can use OpenRC to manage services. For example, SSH can be managed with the rc-service command, without typing the executable path

sudo rc-service sshd start

You can also configure the SSH service to start automatically after logging in to proot-distro.

sudo rc-update add sshd

Method 3: Run a full Linux system virtual machine
#

The ultimate solution is to emulate a full Linux system so that Systemd can run.

OpenRC on Ivon's Blog

Solutions when Termux proot cannot use the systemctl command

Method 1: Start the program directly from the executable path #

Method 2: Switch to a distribution that uses OpenRC #

Method 3: Run a full Linux system virtual machine #

Method 1: Start the program directly from the executable path
#

Method 2: Switch to a distribution that uses OpenRC
#

Method 3: Run a full Linux system virtual machine
#