systemd stopped working suddenly #9063
-
|
Was up and running with a microk8s environment a couple of weeks ago, tried to start it today and am now getting: |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 5 replies
-
|
The following resolved the issue for me: |
Beta Was this translation helpful? Give feedback.
-
|
Hello Mr. GordonSmith Is your environment windoww11+ Ubuntu installed in WSL2 (with the addition to wsl.conf ref: https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/ ) ? I did what is advised in the ref but I get "internal error, please report: running "microk8s" failed: cannot find installed snap "microk8s" at revision 4094: missing file /snap/microk8s/4094/meta/snap.yaml " . I tried both 20.4 and 22.4 versions. Many thanks in advance. Ali |
Beta Was this translation helpful? Give feedback.
-
|
Good morning and thank you very much.
Command line is just like below (actually same as yours) :
sudo snap install microk8s --classic --channel=1.25/stable
And I have /etc/wsl.conf with
[boot]
systemd=true
as written in https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/
And Windows 11 version:
***@***.***
By the way, with https://youtu.be/cWlYe0CE2iU and https://forum.snapcraft.io/t/running-snaps-on-wsl2-insiders-only-for-now/13033 I managed to install microk8s in to my “old” windows 10 laptop last night.
I am still keen to use windows 11 though for my lab env in my desktop PC with 32 gbyte ram.
Thanks a lot again.
Ali
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: Gordon ***@***.***>
Sent: Wednesday, October 26, 2022 5:58 PM
To: ***@***.***>
Cc: ***@***.***>; ***@***.***>
Subject: Re: [microsoft/WSL] systemd stopped working suddenly (Discussion #9063)
Yes (Windows 11 insiders beta) + WSL2 (Ubuntu 22.04). Is this your command line:
sudo snap install microk8s --classic --channel=1.25
?
—
Reply to this email directly, view it on GitHub<#9063 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIBOZVE4HZH7G4IYHIMDX5LWFFBJRANCNFSM6AAAAAARMWL3ZM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
same problem as OP, but the answer did not resolve it for me. |
Beta Was this translation helpful? Give feedback.
-
|
@GordonSmith The original problem with Snap should now be fixed, assuming you are running Ubuntu 22.04? If so, you should be able to:
After this, |
Beta Was this translation helpful? Give feedback.
@GordonSmith The original problem with Snap should now be fixed, assuming you are running Ubuntu 22.04? If so, you should be able to:
sudo rm /etc/binfmt.d/windowsexe.confto remove the temporary workaroundsudo apt update && sudo apt upgrade -yto get Snapd to the latest version with the fixwsl --shutdown(required to reset thebinfmt_miscchange)After this,
snapcommands should be working again.