System has not been booted with systemd Linux Origin: Platform & cloud Last updated 15 Oct 2026

System has not been booted with systemd as init system (PID 1). Can't operate.

You ran systemctl inside an environment without systemd as PID 1 — a Docker container or older WSL.

Exact message you may see System has not been booted with systemd as init system (PID 1). Can't operate.Failed to connect to bus: Host is downSystem has not been booted with systemd
Explore the map of this error Full error map →
Seen on: Linux

Meaning

Containers run your app as PID 1, not systemd, and WSL only enables systemd when configured. Start the service directly (service nginx start, or run the binary) or enable systemd in WSL.

Common causes

  • Running systemctl inside a Docker container
  • WSL without systemd enabled
  • chroot/rescue environments

⚡ Quick fix

  1. In containers, run the process directly in the foreground (CMD)
  2. Use service <name> start where SysV scripts exist
  3. On WSL, enable systemd in /etc/wsl.conf and restart WSL

Detailed fix by platform

WSL

  1. bash
    # /etc/wsl.conf
[boot]
systemd=true
# then in PowerShell: wsl --shutdown

Docker

  1. CMD ["nginx", "-g", "daemon off;"]

How to diagnose

  1. PID 1 — ps -p 1 -o comm=
  2. Environment — Container, WSL or VM?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

0x80370102 — WslRegisterDistribution failed with error: 0x80370102 (virtual machine could not be started) (Windows)0x80370102ACR unauthorized — Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401) (Azure)ACR unauthorizedCannotPullContainerError — ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried (AWS)CannotPullContainerEr…Container failed to start — Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable (Google Cloud / Firebase)Container failed to s…Exited (0) — Docker container exits immediately (Exited (0) / Exited (1) right after start) (Docker)Exited (0)Failed to connect to bus — Failed to connect to bus: No such file or directory (systemctl --user / timedatectl) (Linux)Failed to connect to …Job for x.service failed — Job for nginx.service failed because the control process exited with error code (Linux)Job for x.service fai…Start request repeated too quickly — systemd: Start request repeated too quickly / service hit its start limit (Linux)Start request repeate…System ha…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.