Infra/MLops

[k8s error]System has not been booted with systemd as init system (PID 1). Can't operate.Failed to connect to bus: Host is down

뚜둔뚜둔 2022. 2. 16. 11:17

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

 

 

이 에러가 안 고쳐져서 너무 답답ㅠㅠ

아래의 첫번째 방법이면 대부분 해결 되는듯 하다 

그러나 난 안됨 ㅠㅠ

https://stackoverflow.com/questions/59466250/docker-system-has-not-been-booted-with-systemd-as-init-system

 

Docker System has not been booted with systemd as init system

I have an Ubuntu 18.04 image runing on my docker container. I login into it and installed Openresty. also installed systemd. When I use command "systemctl" I get this error: System has not been bo...

stackoverflow.com

 

두번째 이방법으로 성공하였다

 

Failed to connect to bus: Host is down - WSL 2

Failed to connect to bus: Host is down - WSL 2. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

 sudo systemctl daemon-reload
 
 sudo apt-get update && sudo apt-get install -yqq daemonize dbus-user-session fontconfig

sudo daemonize /usr/bin/unshare --fork --pid --mount-proc /lib/systemd/systemd --system-unit=basic.target

exec sudo nsenter -t $(pidof systemd) -a su - $LOGNAME

snap version

 # snap 가 안될때
 lsb_release -a.
반응형

'Infra > MLops' 카테고리의 다른 글

[helm]helm 사용하기 _2  (6) 2022.03.03
[helm]helm 사용하기 _1  (0) 2022.03.02
[k8s]명령어 정리  (2) 2022.02.15
[k8s] token, certificate-key 찾기  (0) 2022.02.15
[k8s]k8s설치하기  (4) 2022.02.15