Open vadimkantorov opened 3 months ago
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
snap
needs systemd
and wsl1
doesn't support it.
I mean, is it possible to stub out (or uninstall it) snap
in such a way so that the upgrader moves on?
Maybe even snap list
could return 0 exit code and print empty string?
Even if I sudo apt uninstall snap
, then sudo do-release-upgrade
/ noble.tar.gz
reinstalls it and fails while running snap list
. I think a better stub of command snap list
(and maybe others) is needed to proceed...
After the hack I described in https://github.com/ubuntu/WSL/issues/493, the upgrade fails with trying to run some systemd-using postinstall scripts
After the hack I described in ubuntu/WSL#493, the upgrade fails with trying to run some systemd-using postinstall scripts
run command: cd /bin && mv -f systemd-sysusers{,.org} && ln -s echo systemd-sysusers && cd -
then run do-release-upgrade
then success, I had already upgrade from 22.04->24.04->24.10
root@FUJITSU:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.10 Release: 24.10 Codename: oracular root@FUJITSU:~# uname -a Linux FUJITSU 4.4.0-19041-Microsoft #4355-Microsoft Thu Apr 12 17:37:00 PST 2024 x86_64 x86_64 x86_64 GNU/Linux root@FUJITSU:~#
JFYI, this method still works in Nov/24:
1) Apply the changes to bin/systemd-sysusers
suggested by flydt on the comment above;
2) Run the do-release-upgrade
command until it fails. Don't exit the window.
3) In the console history, copy the path to the temporary file DistUpgradeQuirks.py
.
4) In another terminal, edit the DistUpgradeQuirks.py
file. Find the line relative to the exception handling for the command snap list
(search for ['snap', 'list']
) mentioned by vadimkantorov, and apply his suggestion of changing the exception handling from except FileNotFoundError:
by only exception:
, making the code ignore any exceptions from this command.
5) Go back to the do-release-upgrade
window and chose to resurrect the current window. It will try the upgrading process again using the same temporary file (that's what we want). If any errors appear after pressing 'r' to resurrect the window, continue by pressing 'y' (so you answer 'y' when the scripts asks you if you want to continue a few seconds later).
6) Continue the installation!
Thank you all for the knowledge!! WSL1 is a very impressive tech. I'm really sad that it's been being discontinued by MS.
Sorry, I am newbie here, but I bypassed with this script: `root@ffmpeg2:/home/troland# cat /usr/bin/snap
if [ "$1" == "list" ]; then echo "Name Version Rev Tracking Publisher Notes" else echo "snap: command not found: $*" fi`
I don't like edit py files and don't use snap
Windows Version
Microsoft Windows [Version 10.0.22631.4037]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
WSL version: 2.2.4.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.61 MSRDC version: 1.2.5326 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26091.1-240325-1447.ge-release Windows version: 10.0.22631.4037
Repro Steps
Expected Behavior
Ubuntu 24.04 installs in one way or another
Actual Behavior
Complete breakage as it seems to depend on
snap list
which prints this:I would propose at least
snap list
prints an empty list or something else reasonable.Is it possible to upgrade to Ubuntu 24.04 in some other way to bypass
snap
problems?I like WSLv1 on my Laptop because it's fast, lightweight and doesn't require Hyper-V or a full VM and uses the regular processes without a separate memory allocated for the VM.
Diagnostic Logs
No response