Closed krachynski closed 8 months ago
I doesn't know much about winget, does it use our official podman setup.exe to install? If not this is likely not under our control.
it does, but the winget package itself is specifying a dependency on this windows feature. which requires an elevated prompt to enable before running the setup.exe
oh. I didn't realize that I hadn't included the log for the successful elevated prompt
❯ winget install RedHat.Podman
Found Podman [RedHat.Podman] Version 4.9.3
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:
- Windows Features
Microsoft-Windows-Subsystem-Linux
Enabling [Microsoft-Windows-Subsystem-Linux]...
Successfully enabled Windows Features dependencies
Downloading https://github.com/containers/podman/releases/download/v4.9.3/podman-4.9.3-setup.exe
██████████████████████████████ 30.9 MB / 30.9 MB
Successfully verified installer hash
Starting package install...
Successfully installed
@n1hility Is this something that is set by our installer?
Podman can be used as remote client only without any machine so we shouldn't force WSL on users
This is something the package is specifying I agree it should not be required.
@krachynski if you are interested in sending a PR to them this would be a small one requesting they drop this:
Closing is that is not an issue on our side then
microsoft/winget-pkgs#144380
Issue Description
While recently updating my system to report a bug on Podman Desktop's Kind extension, I discovered that Podman's winget package now requires WSL to be enabled and refuses to install if run from a non-elevated prompt.
I know Podman Desktop requires WSL in order to run, I would expect to be able to install podman for connecting to remote podman systems without needing WSL.
Steps to reproduce the issue
winget install RedHat.Podman-Desktop
winget install RedHat.Podman
Describe the results you received
Describe the results you expected
I expected this to just run in a non-elevated prompt the way it's been doing until 4.9.3
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Windows 11 Pro 23H2 (22631.3155)
WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3155
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting