Alpine Linux based WSL distribution. Supports multi-install. Lightest WSL distribution. yuk7/AlpineWSL. Install Compose on Linux systems. On Linux, you can download the Docker Compose binary from the Compose repository release page on GitHub. Follow the instructions from the link, which involve running the curl command in your terminal to download the binaries. These step-by-step instructions are also included below.
Before you start using Yarn, you'll first need to install it on your system. There are many different ways to install Yarn, but a single one is recommended and cross-platform:Install via npm
It is recommended to install Yarn through the npm package manager, which comes bundled with Node.js when you install it on your system.
Once you have npm installed you can run the following both to install and upgrade Yarn:
Alternatives
Alpine
On Alpine Linux (3.6+), you can install Yarn with apk.
Currently, there are no Alpine packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Arch Linux
On Arch Linux, Yarn can be installed through the official package manager.
Currently, there are no Arch packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
CentOS / Fedora / RHEL
On CentOS, Fedora and RHEL, you can install Yarn via our RPM package repository.
If you do not already have Node.js installed, you should also configurethe NodeSource repository:
Then you can simply:
Currently, there are no RPM packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Debian / Ubuntu
On Debian or Ubuntu Linux, you can install Yarn via our Debian packagerepository. You will first need to configure the repository:
On Ubuntu 16.04 or below and Debian Stable, you will also need to configure the NodeSource repository to get a new enough version of Node.js.
Then you can simply:
Note: Ubuntu 17.04 comes with cmdtest installed by default. If you’re getting errors from installing yarn, you may want to run sudo apt remove cmdtest first. Refer to this for more information.
If using nvm you can avoid the node installation by doing:
Note: Due to the use of nodejs instead of node name in some distros, yarn might complain about node not being installed. A workaround for this is to add an alias in your .bashrc file, like so: alias node=nodejs. This will point yarn to whatever version of node you decide to use.
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Gentoo Linux
On Gentoo Linux, you can install Yarn with portage.
Currently, there are no Gentoo packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
macOS
Homebrew
You can install Yarn through the Homebrew package manager.This will also install Node.js if it is not already installed.
If you use nvm or similar, you should ensure that your PATH lists nvm’s shims before the version of Node.js installed by Homebrew.
MacPorts
You can install Yarn through MacPorts.This will also install Node.js if it is not already installed.
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Currently, there are no Homebrew or MacPorts packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Upgrade Yarn
Yarn will warn you if a new version is available.To upgrade Yarn, you can do so with Homebrew.
Solus
On Solus, you can install yarn via the Solus repository.
Currently, there are no Solus packages available for RC or nightly builds of Yarn. Please use the tarball:
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Windows
There are three options for installing Yarn on Windows.
Download the installer
This will give you a .msi file that when run will walk you through installingYarn on Windows.
If you use the installer you will first need to installNode.js.
Download InstallerDownload Installer (RC)Download Installer (Nightly)
Install via Chocolatey
Chocolatey is a package manager for Windows.You can install Chocolatey by followingthese instructions.
Once you have Chocolatey installed, you may install yarn by running thefollowing code in your console:
This will also ensure that you have Node.js installed.
Install via Scoop
Scoop is a command-line installer for Windows.You can install Scoop by followingthese instructions.
Once you have Scoop installed, you may install yarn by running thefollowing code in your console:
If Node.js is not installed, scoop will give you a suggestion to install it.Example:
Notice
Please whitelist your project folder and the Yarn cache directory (%LocalAppData%Yarn) in your antivirus software, otherwise installing packages will be significantly slower as every single file will be scanned as it’s written to disk.
Alternatives
If you are using another OS or one of the other options specific to your OSwill not work for you, there are a couple of alternatives. You will need toinstall Node.js if you don’t already have it installed.
On common Linux distributions such as Debian, Ubuntu and CentOS, it isrecommended to install Yarn via our packages instead.
Installation Script
One of the easiest ways to install Yarn on macOS and generic Unix environmentsis via our shell script. You can install Yarn by running the following code inyour terminal:
The installation process includes verifying a GPG signature.View the source on GitHub
You can also specify a version by running the following code in your terminal:
See the releases for possible versions.
Manual Install via tarball
You can install Yarn by downloading a tarball andextracting it anywhere.
Before extracting Yarn, it is recommended that you verify the tarball using GPG:
Path Setup
Unix/Linux/macOS
If Yarn is not found in your PATH, follow these steps to add it and allow it to be run from anywhere.
Note: your profile may be in your .profile, .bash_profile, .bashrc, .zshrc, etc.
- Add this to your profile:
export PATH='$PATH:/opt/yarn-[version]/bin'(the path may vary depending on where you extracted Yarn to) - In the terminal, log in and log out for the changes to take effect
To have access to Yarn’s executables globally, you will need to set up the PATH environment variable in your terminal. To do this, add export PATH='$PATH:`yarn global bin`' to your profile, or if you use Fish shell, simply run the command set -U fish_user_paths (yarn global bin) $fish_user_paths
Windows
You will need to set up the PATH environment variable in your terminal to have access to Yarn’s binaries globally.
Add set PATH=%PATH%;C:.yarnbin to your shell environment.
Check installation
Check that Yarn is installed by running:
-->All packages are available on our GitHub releases page. After the package is installed, runpwsh from a terminal. Run pwsh-preview if you installed aPreview release.
Note
PowerShell 7 is an in-place upgrade that removes PowerShell Core 6.x.
The /usr/local/microsoft/powershell/6 folder is replaced by /usr/local/microsoft/powershell/7.
If you need to run PowerShell 6 side-by-side with PowerShell 7, reinstall PowerShell 6 using thebinary archive method.
For Linux distributions that aren't officially supported, you can try to install PowerShell usingthe PowerShell Snap Package. You can also try deploying PowerShell binaries directly usingthe Linux tar.gz archive, but you would need to set up the necessary dependencies based onthe OS in separate steps.
Officially supported platform releases for PowerShell 7.1
- Ubuntu 16.04/18.04/20.04 (including ARM64)
- Ubuntu 19.10 (via Snap package)
- Debian 9/10
- CentOS and RHEL 7/8
- Fedora 30
- Alpine 3.11+ (including ARM64)
Officially supported platform releases for PowerShell 7.0
- Ubuntu 16.04
- Ubuntu 18.04 and 20.04
- Debian 8
- Debian 9
- Debian 10
- Alpine 3.9 and 3.10
- CentOS 7
- Red Hat Enterprise Linux (RHEL) 7
- Fedora 28
- Fedora 29
- Fedora 30
- openSUSE 42.3
- openSUSE Leap 15
Community supported releases
- Ubuntu 18.10
- Ubuntu 19.10 and 20.10
- Arch Linux
- Kali
- Raspbian (experimental)
Alternate install methods
- Snap Package
- Binary Archives
- .NET Global tool
Ubuntu 16.04
Installation via Package Repository - Ubuntu 16.04
PowerShell for Linux is published to package repositories for easy installation and updates.
The preferred method is as follows:
As superuser, register the Microsoft repository once. After registration, you can updatePowerShell with sudo apt-get install powershell.
Installation via Direct Download - Ubuntu 16.04
Download the Debian package powershell_7.1.3-1.ubuntu.16.04_amd64.deb from the releases pageonto the Ubuntu machine.
Then, in the terminal, execute the following commands:
Note
The dpkg -i command fails with unmet dependencies. The next command, apt-get install -fresolves these issues then finishes configuring the PowerShell package.
Uninstallation - Ubuntu 16.04
Ubuntu 18.04
Installation via Package Repository - Ubuntu 18.04
PowerShell for Linux is published to package repositories for easy installation and updates.
The preferred method is as follows:
As superuser, register the Microsoft repository once. After registration, you can updatePowerShell with sudo apt-get install powershell.
Installation via Direct Download - Ubuntu 18.04
Download the Debian package powershell_7.1.3-1.ubuntu.18.04_amd64.deb from the releases pageonto the Ubuntu machine.
Then, in the terminal, execute the following commands:
Note
The dpkg -i command fails with unmet dependencies. The next command, apt-get install -fresolves these issues then finishes configuring the PowerShell package.
Uninstallation - Ubuntu 18.04
Ubuntu 20.04
Installation via Package Repository - Ubuntu 20.04
Install Curl Alpine Linux Server
PowerShell for Linux is published to package repositories for easy installation and updates.
The preferred method is as follows:
As superuser, register the Microsoft repository once. After registration, you can updatePowerShell with sudo apt-get install powershell.
Installation via Direct Download - Ubuntu 20.04
Download the Debian package powershell_7.1.3-1.ubuntu.20.04_amd64.deb from the releases pageonto the Ubuntu machine.
Then, in the terminal, execute the following commands:
Note
The dpkg -i command fails with unmet dependencies. The next command, apt-get install -fresolves these issues then finishes configuring the PowerShell package.
Uninstallation - Ubuntu 20.04
Ubuntu 18.10
Installation is supported via snapd. For instructions, see Snap Package.
Note
Ubuntu 18.10 is an interim release that'scommunity supported.
Ubuntu 19.10 and 20.10
Installation is supported via snapd. For instructions, see Snap Package.
Note
Ubuntu 19.10 is an interim release that'scommunity supported.
Debian 8
Installation via Package Repository - Debian 8
PowerShell for Linux is published to package repositories for easy installation and updates.
The preferred method is as follows:
As superuser, register the Microsoft repository once. After registration, you can update PowerShellwith sudo apt-get install powershell.
Debian 9
Installation via Package Repository - Debian 9
PowerShell for Linux is published to package repositories for easy installation and updates.
The preferred method is as follows:
As superuser, register the Microsoft repository once. After registration, you can update PowerShellwith sudo apt-get install powershell.
Installation via Direct Download - Debian 9
Download the Debian package powershell_7.1.3-1.debian.9_amd64.deb from the releases pageonto the Debian machine.
Then, in the terminal, execute the following commands:
Uninstallation - Debian 9
Debian 10
Note
Debian 10 is only supported in PowerShell 7.0 and newer.
Installation via Package Repository - Debian 10
PowerShell for Linux is published to package repositories for easy installation and updates.
Install Curl Alpine Linux Vm
The preferred method is as follows:
Installation via Direct Download - Debian 10
Download the tar.gz package powershell-7.1.3-linux-x64.tar.gz from the releases pageonto the Debian machine.
Then, in the terminal, execute the following commands:
Alpine 3.9 and 3.10
Note
Alpine 3.9 and 3.10 are only supported in PowerShell 7.0 and newer.
Installation via Direct Download - Alpine 3.9 and 3.10
Download the tar.gz package powershell-7.1.3-linux-alpine-x64.tar.gz from the releases page ontothe Alpine machine.
Then, in the terminal, execute the following commands:
CentOS 7
Installation via Package Repository (preferred) - CentOS 7
PowerShell for Linux is published to official Microsoft repositories for easy installation andupdates.
As superuser, register the Microsoft repository once. After registration, you can update PowerShellwith sudo yum update powershell.
Installation via Direct Download - CentOS 7
Using CentOS 7, download the RPM package powershell-7.1.3-1.rhel.7.x86_64.rpm from the releasespage onto the CentOS machine.
Then, in the terminal, execute the following commands:
You can install the RPM without the intermediate step of downloading it:
Uninstallation - CentOS 7
Red Hat Enterprise Linux (RHEL) 7
Installation via Package Repository (preferred) - Red Hat Enterprise Linux (RHEL) 7
PowerShell for Linux is published to official Microsoft repositories for easy installation andupdates.
As superuser, register the Microsoft repository once. After registration, you can update PowerShellwith sudo yum update powershell.
Installation via Direct Download - Red Hat Enterprise Linux (RHEL) 7
Download the RPM package powershell-7.1.3-1.rhel.7.x86_64.rpm from the releases page ontothe Red Hat Enterprise Linux machine.
Then, in the terminal, execute the following commands:
You can install the RPM without the intermediate step of downloading it:
Uninstallation - Red Hat Enterprise Linux (RHEL) 7
openSUSE
Installation - openSUSE 42.3
Installation - openSUSE Leap 15
Uninstallation - openSUSE 42.3, openSUSE Leap 15
Fedora
Note
Fedora 28 is only supported in PowerShell 6.1 and newer.
Note
Fedora 29 and 30 are only supported in PowerShell 7.0 and newer.
Installation via Package Repository (preferred) - Fedora 28, 29, and 30
PowerShell for Linux is published to official Microsoft repositories for easy installation andupdates.
Installation via Direct Download - Fedora 28, 29, and 30
Download the RPM package powershell-7.1.3-1.rhel.7.x86_64.rpm from the releases page onto theFedora machine.
Then, in the terminal, execute the following commands:
You can install the RPM without the intermediate step of downloading it:
Uninstallation - Fedora 28, 29, and 30
Arch Linux
Note
Arch support is not officially supported by Microsoft and is maintained by the community.
PowerShell is available from the Arch Linux User Repository (AUR).
- It can be compiled with the latest tagged release
- It can be compiled from the latest commit to master
- It can be installed using the latest release binary
Packages in the AUR are community maintained; there's no official support.
For more information on installing packages from the AUR, see theArch Linux wiki orUsing PowerShell in Docker.
Install Curl Alpine Linux Download
Snap Package
Getting snapd
snapd is required to run snaps. Use these instructionsto make sure you have snapd installed.
Installation via Snap
PowerShell for Linux is published to the Snap store for easyinstallation and updates.
The preferred method is as follows:
To install a preview version, use the following method:
After installation, Snap will automatically upgrade. You can trigger an upgrade usingsudo snap refresh powershell or sudo snap refresh powershell-preview.
Uninstallation
or
Kali
Note
Kali support is not officially supported by Microsoft and is maintained by the community.
Installation - Kali
Uninstallation - Kali
Support for Arm processors
PowerShell can be installed on some Linux distributions. PowerShell is dependent on .NET support ofArm. PowerShell is supported on the following distributions:
- Alpine Linux v3.11+ - .NET supports Arm64 but there is no installable package for PowerShell atthis time
- Raspbian - see the installation instructions below
- Debian v9+ - supports Arm32 and Arm64 using the Binary Archive installationmethod
- Ubuntu 20.10, 20.04, 18.04, 16.04 - supports Arm32 and Arm64 using theBinary Archive installation method
Raspbian
Currently, PowerShell is only supported on Raspbian Stretch.
CoreCLR and PowerShell will only work on Pi 2 and Pi 3 devices as other devices, likePi Zero, have an unsupported processor.
Download Raspbian Stretch and follow theinstallation instructionsto get it onto your Pi.
Installation - Raspbian
Optionally, you can create a symbolic link to start PowerShell without specifying the path to thepwsh binary.
Install Curl Alpine Linux Usb
Uninstallation - Raspbian
Installing Preview Releases
When installing a PowerShell Preview release for Linux via a Package Repository, the package namechanges from powershell to powershell-preview.
Installing via direct download doesn't change, other than the file name.
The following table contains the commands to install the stable and preview packages using thevarious package managers:
| Distribution(s) | Stable Command | Preview Command |
|---|---|---|
| Ubuntu, Debian | sudo apt-get install -y powershell | sudo apt-get install -y powershell-preview |
| CentOS, RedHat | sudo yum install -y powershell | sudo yum install -y powershell-preview |
| Fedora | sudo dnf install -y powershell | sudo dnf install -y powershell-preview |
Install as a .NET Global tool
If you already have the .NET Core SDK installed, it's easy to install PowerShellas a .NET Global tool.
The dotnet tool installer adds ~/.dotnet/tools to your PATH environment variable. However, thecurrently running shell does not have the updated PATH. You should be able to start PowerShellfrom a new shell by typing pwsh.
Binary Archives
PowerShell binary tar.gz archives are provided for Linux platforms to enable advanced deploymentscenarios.
Note
You can use this method to install any version of PowerShell including the latest:
- Stable release: https://aka.ms/powershell-release?tag=stable
- Preview release: https://aka.ms/powershell-release?tag=preview
- LTS release: https://aka.ms/powershell-release?tag=lts
Dependencies
PowerShell builds portable binaries for all Linux distributions. But, .NET Core runtime requiresdifferent dependencies on different distributions, and PowerShell does too.
The following chart shows the .NET Core 2.0 dependencies that are officially supported on differentLinux distributions.
| OS | Dependencies |
|---|---|
| Ubuntu 16.04 | libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu55 |
| Ubuntu 17.10 | libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu57 |
| Ubuntu 18.04 | libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu60 |
| Debian 8 (Jessie) | libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu52 |
| Debian 9 (Stretch) | libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.2, libicu57 |
| CentOS 7 Oracle Linux 7 RHEL 7 | libunwind, libcurl, openssl-libs, libicu |
| openSUSE 42.3 | libcurl4, libopenssl1_0_0, libicu52_1 |
| openSUSE Leap 15 | libcurl4, libopenssl1_0_0, libicu60_2 |
| Fedora 27 Fedora 28 | libunwind, libcurl, openssl-libs, libicu, compat-openssl10 |
To deploy PowerShell binaries on Linux distributions that aren't officially supported, you need toinstall the necessary dependencies for the target OS in separate steps. For example, ourAmazon Linux dockerfile installs dependencies first, and then extracts theLinux tar.gz archive.
Installation - Binary Archives
The following example shows the steps for installing the x64 binary archive. You must choose thecorrect binary archive that matches the processor type for your platform.
- powershell-7.1.3-linux-arm32.tar.gz
- powershell-7.1.3-linux-arm64.tar.gz
- powershell-7.1.3-linux-x64.tar.gz
Linux
Install Curl Alpine Linux Ubuntu
Uninstalling binary archives
Paths
$PSHOMEis/opt/microsoft/powershell/7/- User profiles are read from
~/.config/powershell/profile.ps1 - Default profiles are read from
$PSHOME/profile.ps1 - User modules are read from
~/.local/share/powershell/Modules - Shared modules are read from
/usr/local/share/powershell/Modules - Default modules are read from
$PSHOME/Modules - PSReadLine history is recorded to
~/.local/share/powershell/PSReadLine/ConsoleHost_history.txt
The profiles respect PowerShell's per-host configuration, so the default host-specific profilesexists at Microsoft.PowerShell_profile.ps1 in the same locations.
PowerShell respects the XDG Base Directory Specification on Linux.
Installation support
Microsoft supports the installation methods in this document. There may be other methods ofinstallation available from other sources. While those tools and methods may work, Microsoft cannotsupport those methods.