installing k3 - getting the following error : System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

 

Hit this issue trying to get k3 working on a Windows Subsystem Linux. 

wsl.conf 

Ensure you have the following configuration in your /etc/wsl.conf

Add the following:
[boot]
systemd=true

From a powershell command prompt, you may need to do 

wsl --update 

wsl --shutdown

Then restart your wsl and run the k3 install script :- 

curl -sfL https://get.k3s.io | sh -


And that should be it. Notice the following output from kubectl.




Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more