Step 4 - Next, we will install the required Python packages as outlined in the PowerCLI User Guide using pip by running the following command:Īrch -x86_64 /usr/local/bin/pip3.7 install six psutil lxml pyopenssl Step 3 - The x86 version of brew will be located under /usr/local/bin and run the following command to install Python 3.7:Īrch -x86_64 /usr/local/bin/brew install Note: The use of the arch command to install x86 version brew was thanks to this StackOverflow answer. Step 2 - Install the x86 version of Brew, which will be required to then install the x86 version of Python by running the following command:Īrch -x86_64 /bin/bash -c "$(curl -fsSL )" Softwareupdate -install-rosetta -agree-to-license
Step 1 - Open Terminal and install Rosetta, which is a utility that Apple provides to run x86 binaries on the Apple Silicon. I only bring up this detail because it ultimately helped me figure out how to get PowerCLI 13.0 working on the Apple M1, especially with the additional Python requirement which includes one specific shared library that is dependent on the x86 architecture. While the external dependency of Python is new, the requirement for Python to use these cmdlets has always been there and earlier releases of PowerCLI, it was just packaged as part of PowerCLI. The official PowerCLI User Guide contains instructions on how to install the Python runtime and the required packages across the three OS platforms (Windows, macOS and Linux). PowerCLI 13.0 now has an external dependency on Python 3.7.x runtime, which is specific when needing to use the new Image Builder and Auto Deploy cmdlets. Part of the challenge is also due to the new requirement with latest PowerCLI 13.0 release, which folks should be aware of as it does have additional implications in how you manage and deploy PowerCLI within your organizations. I have both an x86 macOS system and the new Apple Silicon M1 (Arm) and of course, I wanted to have PowerCLI running on both systems! While the installation/upgrade of PowerCLI for x86 is trivial, it was definitely less so on the M1. PowerCLI 13.0 was just released about a week ago and I have been using it like crazy, especially with the new Image Builder and Auto Deploy cmdlets, which have now been ported over to PowerShell Core and finally removing the Windows-only dependency for these specific cmdlets! 😀
0 kommentar(er)
