install linux distribution under wsl [migrated] - installation

This question was migrated from Stack Overflow because it can be answered on Super User.
Migrated 25 days ago.
I am trying to use WSL under Windows 10 Pro, and while WSL itself was installed without a problem, I cannot install any Linux distribution under it.
PS C:\WINDOWS\system32> wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19042.2486
PS C:\WINDOWS\system32> wsl -l
Windows Subsystem for Linux has no installed distributions.
Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install <Distro>' to install.
Distributions can also be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Error code: Wsl/WSL_E_DEFAULT_DISTRO_NOT_FOUND
PS C:\WINDOWS\system32> wsl -l -o
The following is a list of valid distributions that can be installed.
Install using 'wsl.exe --install <Distro>'.
NAME FRIENDLY NAME
Ubuntu Ubuntu
Debian Debian GNU/Linux
kali-linux Kali Linux Rolling
SLES-12 SUSE Linux Enterprise Server v12
SLES-15 SUSE Linux Enterprise Server v15
Ubuntu-18.04 Ubuntu 18.04 LTS
Ubuntu-20.04 Ubuntu 20.04 LTS
Ubuntu-22.04 Ubuntu 22.04 LTS
OracleLinux_8_5 Oracle Linux 8.5
OracleLinux_7_9 Oracle Linux 7.9
PS C:\WINDOWS\system32> wsl --install Ubuntu
Installing: Ubuntu
Error: 0x80244018 0.0% ]
Error code: Wsl/InstallDistro/0x80244018
PS C:\WINDOWS\system32> wsl --install Debian
Installing: Debian GNU/Linux
Error: 0x80244018 0.0% ]
Error code: Wsl/InstallDistro/0x80244018
PS C:\WINDOWS\system32>
I did try disabling proxy, as I found in one of the posts, but instead of Error: 0x80244018 got Catastrophic Failure.
Can anybody recommend what I can do to install a distro?

As I believe you've discovered (from your proxy comment), this error is usually due to a failure in the Windows Update service. By default, WSL uses this service to install distributions from the Microsoft Store, but many other Windows components and applications use the service as well.
While the information below may help with WSL, it's likely that you have a more significant issue that you'll need to resolve. If that's the case, you'll probably want to post a new question that is broader in scope, rather than just this one that focuses on WSL.
That said, my suggested workaround for installing WSL distributions would be to try:
wsl --install --web-download Debian
The --web-download option skips the Store (and shouldn't use the Windows Update service), and will download the distribution directly then install it.
Alternatively, if you can get access to a working Docker installation apart from this system, you could use the steps found in Import any Linux distribution to use with WSL.

Related

Heroku: understanding what version of Linux Kernel is used

I'm confused about which Linux Kernel is used to run Heroku apps, and the docs don't seem to spell it out.
Heroku offers "stacks" synced to Ubuntu LTS releases, and I just upgraded one of our apps from Heroku-18 (Ubuntu 18.04) to Heroku-20 (Ubuntu 20.04), and I was curious as to whether that would constitute a Linux Kernel upgrade.
So, before I upgraded the stack, I logged into a dyno and ran the following (on Heroku-18):
~ $ cat /proc/version_signature
Ubuntu 4.4.0-1097.102-aws 4.4.262
~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
and then after upgrading to Heroku-20:
~ $ cat /proc/version_signature
Ubuntu 4.4.0-1097.102-aws 4.4.262
~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
So, upgrading did NOT change the Kernel version 4.4.262, which appears to have been released March 2021 (10 months ago).
The docs for Ubuntu 20 say that it's based on LTS Linux 5.4, so why is Heroku continuing to use the older 4.4.x Kernel? When might this be upgraded, and how might it be communicated?
I was also curious what the Kernel version would be for Heroku's container stack; I'm not sure how to find this out, but given the above, I'm betting that it too would be 4.4.x. This matters to me because I'm curious to try out io_uring and some other recent Linux Kernel developments, but it seems like I'd have to wait a long time to try out something like that on Heroku.

apt in Linux Subsystem for Windows 10 is failing with 404 Not Found

OK, so this is my first SO question so I'm gonna try my best to lay this out.
I have a Windows 10 laptop on which I am trying to install gcc. I have in the past tried alternatives such as netbeans, cygwin and various emulators and virtual machines all to no avail.
What has been working so far is that I enabled the 'new' windows developer mode which allowed me to download a Linux bash shell from the windows store. It works for all the regular Linux commands, but doesn't have gcc installed.
When I type in gcc (or gcc --version) in the shell, it prints the following line:
The program 'gcc' is currently not installed. You can install it by typing:
sudo apt install gcc
Which I tried, it then ran through a bunch of installer stuff but consistently seemed to run into errors such as the following:
Err:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdpkg- >perl all 1.18.4ubuntu1.2
404 Not Found [IP: INSERT IP ADDRESS HERE ]
where the ip address is different on each error line.
It ultimately fails with the following line:
Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I have tried but again I get the same kinds of errors as above.
I would really like to get gcc working in the Windows/Linux shell as it is working great for everything else, and I'm trying to keep the number of programs on my computer to a minimum.
Does anyone know why this isn't working, or how (if possible) I can make it work?
P.S I do need it to be gcc because of school reasons
For what it's worth: I landed on this SO topic after having a similar issue.
What fixed it for me was to run
sudo apt-get update
sudo apt-get upgrade
I guess the repo URLs were too old, even though my Ubuntu was in a recent version.
I just ran into the same thing attempting to install python-pip. According to this article, this happens when you have the Windows 10 Anniversary Update (older) instead of the Creators update (newer). The solution is to either uninstall and re-install Ubuntu, or upgrade it (from 14.04 to 16.04). I found the upgrade to be simple and painless:
sudo do-release-upgrade
To check what you have, before and after via:
lsb_release -a
I had the same problem. Pinging the IP resulted in no response and visiting the website returned a 404.
I found a ppa with most current GCC and registered the PPA and was able to successfully install GCC with it; ppa website. I used GCC to build some software I wanted that was not found with apt-get.
From their page:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
Try to run Ubuntu application in Windows with an option "Run as Administrator".

Install Metatrader 5 on Ubuntu 17.04

I try to install Metatrader 5, on Ubuntu 17.04 (64-bit).
I get stuck, and need somebody to help me to solve this problem.
I've installed wine-2.0.1, which is the latest stable version at the moment, and it's for 64-bit.
Finally, after successfully installing Metatrader 5, on launching the application appears an error window: terminal64.exe, with message:
A debugger has been found running in your system.
Please, unload it from memory and restart your programm.
On wiki.winehq.org, I've found that is needed to install 2 separate versions of wine: 32-bit and 64-bit. I try to do all like in:
https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu
, but at the stage "Build 64-bit Wine", for: make clean, I got:
make: *** No rule to make target 'clean'. Stop.
There is a way to really install mt5 on Ubuntu 17.04 ?
Just installed it after suffering a little bit. After seeing many requests from the installer to provide a proxy!
First install the latest Wine from the instructions given in its website for Ubuntu (this is the one that will work!)
sudo dpkg --add-architecture i386
wget -nc https://dl.winehq.org/wine-builds/Release.key
sudo apt-key add Release.key sudo apt-add-repository
https://dl.winehq.org/wine-builds/ubuntu/
sudo apt-get update
Stable branch:
sudo apt-get install --install-recommends winehq-stable
Configure Wine to 32 bits (only your user)
WINEARCH=win32 WINEPREFIX=~/.wine32 wineboot
Install Metatrader 5
WINEPREFIX=~/.wine32 wine start /unix /path/to/mt5setup.exe
Happiness
Finally to run MetaTrader 5 add the following to your .bashrc our .profile. And type metatrader on your terminal.
export WINEPREFIX=~/.wine32
alias metatrader='wine start "C:\program files\metatrader 5\terminal.exe"'
Thanks to #Kaleshwar Chand
I recently installed metatrader5 on ubuntu 17.04, using the instructions found on mql5 thread
basically mt5 is 32 bit and your ubuntu is 64 bit so you need to change arch to 32 bit to install/use it properly
enter into terminal
WINEARCH=win32 WINEPREFIX=/home/user/.wine32 wineboot
replace user with your username
then install with
WINEPREFIX=/home/user/.wine32 wine start /unix /path/to/mtsetup.exe
again replace user with your username
I am running MT5 on Arch,
in my case, a 64bit wineprefix is needed for connect with other apis so...
For install and run it correctly I installed:
wine, wine-mono, wine_gecko, winetricks, playonlinux
winetircks corefonts, winetricks winhttp
libgnutls allowed to skip the required proxy error
MT5 was installed throught playonlinux on a 64bit wineprefix
Follow the steps from office winehq at https://wiki.winehq.org/
and find your OS you are using
Android (WineHQ binary packages for Android)
Ubuntu (WineHQ binary packages for Ubuntu 16.04, 18.04, 19.04, and 19.10)
Debian (WineHQ binary packages for Debian Stretch, Buster, and Bullseye)
Fedora (WineHQ binary packages for Fedora 30 and 31)
MacOS (WineHQ binary packages for macOS 10.8 through 10.14)

VMWare 12.5 doesn't like my gcc-6 under Mint

I'm spending way too muhc time on trying to figure this out, so I decided to ask you guys for a little help.
I downloaded VMWare Workstation 12.5.5 on kernel 4.10.8 (Linux Mint 18.1).
A popup show up saying I don't have gcc >= 6.2.0.
After trying to compile it I realised there's a version hosted on a ppa:
deb http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial
main
sudo apt update
sudo apt install gcc-6
I relaunch vmware and I still get this error. Entering the path manually to /usr/bin/gcc-6 doesn't work either. /usr/bin/gcc-6 -v gives me gcc version 6.2.0 20160901 (Ubuntu 6.2.0-3ubuntu11~16.04)
How can I run VMware on my machine? Thanks! :D

libvirt and VirtualBox on OS X

I'm trying to access VirtualBox through libvirt on OS X (Lion). I installed libvirt 0.9.4 using Homebrew. However, libvirt fails to connect to VirtualBox:
# virsh -c vbox:///session
error: internal error unable to initialize VirtualBox driver API
error: failed to connect to the hypervisor
In a similar SO question about Ubuntu, the answer was that the Ubuntu libvirt package doesn't build support for VirtualBox. How can I check if this is the problem in the case of the Homebrew package, or if it's a different issue? If it's the same problem, how do I rebuild the Homebrew package with VirtualBox support?
Edit: libvirt 0.9.7 has been released, and I no longer get this error.
Your libvirt is build with VirtualBox support. I can tell because the error message you see comes from the VirtualBox driver in libvirt.
There was a similar problem reported on the libvirt users maling list today. The problem there was that support for VirtualBox 4.1 was added quite recently to libvirt. It's not in a released version yet and will be part of the next libvirt release 0.9.7.
To get some more useful information try running this:
LIBVIRT_LOG_FILTERS=1:vbox virsh -c vbox:///session
I suspect that you have VirtualBox 4.1 installed, but libvirt 0.9.4 supports only up to VirtualBox 4.0.
You can either a) upgrade your libvirt to current git version (that supports VirtualBox 4.1), or b) wait for the next libvirt release (it's expected in this week) or c) downgrade your VirtualBox version to 4.0 to fix this, assuming your problem is really as I suspect.

Resources