Solve Error 'System has not been booted with systemd as init system (PID 1)' in a Docker Container

#docker #systemd #pid1error
If you are getting the error in a Docker container, this solution is for you.
𝗡𝗼𝘁𝗲 : The solution is for new containers. It does not show you to solve in the existing container.
00:00 Where did you do wrong
03:00 Reproducing the error
03:37 What did you do wrong
04:26 Solving the error
05:52 Verification that there will be no error again
08:24 Proof there is no error
𝐚) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗨𝗯𝘂𝗻𝘁𝘂
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
docker run -d --name Linuxamination --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro jrei/systemd-ubuntu:20.04
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
docker exec -it Linuxamination bash
𝐛) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗖𝗲𝗻𝘁𝗢𝗦
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
docker run -d --name linuxaminationC8 --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro alekseychudov/centos8-systemd
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
docker exec -it linuxaminationC8 bash
𝐜) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝐃𝐞𝐛𝐢𝐚𝐧
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
sudo docker run -d --name systemd-debian --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro jrei/systemd-debian:11
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
sudo docker exec -it systemd-debian bash
𝐝) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗳𝗲𝗱𝗼𝗿𝗮
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
sudo docker run -d --name systemd-fedora --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro jrei/systemd-fedora
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
sudo docker exec -it systemd-fedora bash
𝗲) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗥𝗲𝗱𝗵𝗮𝘁 𝗟𝗶𝗻𝘂𝘅
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
sudo docker run -d --name linuxamination --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro registry.access.redhat.com/ubi8/ubi-init:8.1
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
sudo docker exec -it linuxamination bash
𝐟) 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝐀𝐥𝐦𝐚𝐋𝐢𝐧𝐮𝐱
𝐏𝐮𝐥𝐥 𝐈𝐦𝐚𝐠𝐞 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 :
sudo docker run -d --name almalinuxamination --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro almalinux/8-init
𝐋𝐨𝐠 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 :
sudo docker exec -it almalinuxamination bash
______________________________________________________________
𝐊𝐞𝐲𝐰𝐨𝐫𝐝𝐬
Solution for the docker container systemd error
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
docker systemd pid 1 error
docker systemd boot error
______________________________________________________________
Copyright Free Background Music
Audio Library : Kiss the Sky by Aakash Gandhi

[@sharathkumark9692]

Thank you bro... I was finding this more than a month!!! Finally got 🥳🥳🥳🥳 Thank you soooo much......

[@kevinalexismartinezherrera7004]

How can I connect to the instance with Sql Server Magnament?

[@jakwirloker804]

Which command debian 10??

[@rezamohammadi2494]

thank you so much

[@thongnguyen-pe6fo]

how about rocky linux 8 & 9 ? Please

[@yifanwang5700]

What if the problem was in datahub?

[@suterasharky6788]

i didnt understand im using ubuntu i got my error Error response from daemon: Container 1d189ede279a9278072b65eb7e69fe84106e323917a1ee7d7aae396109098772 is not running, when run docker exec -it Linuxamination bash

[@tmattoneill]

Uh... the first command yields: "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" and obviously I can't start the daemon due to: "System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down"

[@churchstcreations7485]

Trying your Cento8 command and getting "denied: requested access to the resource is denied." Can you let me know?

[@LinuXamination]

Try with sudo docker run -d --name linuxaminationCsys --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro centos/systemd sudo docker exec -it linuxaminationCsys bash

[@jp-uno]

Any thoughts on how to perform this on Redhat Linux container?

[@LinuXamination]

Redhat has ubi-init images for systemd. sudo docker run -d --name imagename --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro registry.access.redhat.com/ubi8/ubi-init:8.1 sudo docker exec -it imagename bash Launched container should not have the issue. or if it has Try with podman podman run -d --name imagename --systemd always --security-opt label=type:test_policy.process registry.access.redhat.com/ubi8/ubi-init This should fix the issue.

[@shaikasif4093]

Brother i need solution for amazon linux aswell

[@hariprasadsugurthi6091]

which command for centos 8 image?

[@LinuXamination]

Docker Centos provides documentation to launch systemd container but I think they have not updated for Centos 8 yet. It is available for Centos 7. As you need Centos 8 systemd images, there are repositories available for systemd Centos 8 image. Try this. docker run -d --name linuxaminationC8 --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro alekseychudov/centos8-systemd docker exec -it linuxaminationC8 bash When you are inside the container, run command ps aux to see the process. Your PID 1 process will be /usr/lib/systemd/systemd

[@nikhilatammu2036]

Till "ps aux" command it's fine. How it's changed to root@node46698-env-6622208:~# At solving error 5.03. Please help with this.

[@LinuXamination]

Initially container was running with normal ubuntu image. pid 1 was /bin/bash. At 05:03 I logged out from that container. node46698-env is host system. Then I launched new container using that long docker run command and logged into this new container. Here in new container pid 1 is systemd. This solved the issue.

[@nikhilatammu2036]

@@LinuXamination Thanks for the quick reply. Got it. To logged into the container, my container is going to Exited status within seconds. I'm getting error "Error response from daemon: Container id is not running" while trying to execute "docker exec -itd Linuxamination bash". Do you have any solution for this please let me know.

[@LinuXamination]

There are commands for other distributions also available in the description. Try with centos or debian. If still same issue, the issue can be with the host system. You should try this on other server too where docker is installed. Then you can find issue is with the host system or specific container or something else.

[@suterasharky6788]

@@LinuXamination how to find node46698-env is that the system sir?

[@GatoxGaming]

Is it the same for kali

[@LinuXamination]

Kali is also debian based so it should work for it.

[@jagadheeswargangaraju1179]

Hi, I am getting below error in Ubuntu, when i try to enter into the container by "docker exec -it Linuxamination bash" "Error response from daemon: Container ff2115cefd03c398ffa76923e02cef847c57d74d9ae8b6cdc34d96b65e7d3b01 is not running" Please help

[@LinuXamination]

Hi, 1. Run both commands using sudo and change the container name in exec command like L2 2. If it does not solve and you get container not running error again, Try to start the container using command sudo docker start containerid Put the container id in above command. 3. If it is still not solved, try it in some other os container like debian or centos. You can find commands in the description. If it works, issue is with ubuntu container. You need to find some other systemd container of Ubuntu.

[@jagadheeswargangaraju1179]

@@LinuXamination i run both commands using sudo only but getting same error and i run sudo docker start containerid but still same error

[@jagadheeswargangaraju1179]

I have run with some other systemd container ubuntu, but still getting same error, can you please help

[@LinuXamination]

I would suggest to check docker logs why container is not running or follow steps from description to launch centos or debian systemd container, if it works this is the issue with ubuntu systemd container.

[@beldewpie3174]

Replace Linux animation with ur username

[@luanminh4870]

How about Centos 8?

[@LinuXamination]

docker run -d --name linuxaminationC8 --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro alekseychudov/centos8-systemd docker exec -it linuxaminationC8 bash When you are inside the container, run command ps aux to see the process. Your PID 1 process will be /usr/lib/systemd/systemd

[@luanminh4870]

@@LinuXamination but I am running docker desktop on win10, I want to running container centos with privilleged.

[@aldisseia]

for debian 11???

[@LinuXamination]

sudo docker run -d --name systemd-debian --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro jrei/systemd-debian:11 sudo docker exec -it systemd-debian bash pid 1 will be /lib/systemd/systemd

[@aldisseia]

@@LinuXamination thanks...

[@freddymartinez2487]

please for almalinux

[@LinuXamination]

sudo docker run -d --name linuxamination --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro almalinux/8-init sudo docker exec -it linuxamination bash

[@SIAMEInekeidijdnen]

i love india

[@samidill1232]

Bro Kali linux comand

[@LinuXamination]

Hey... If you are searching systemd enabled Kali docker image, I would suggest you to use systemd Debian or Systemd Ubuntu docker image as Kali is also debian based distribution. If your host system is Kali where docker is installed, you can find different distributions systemd enabled docker images from the description.