You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a fresh Podman v5.1 installation, the windows installer creates the file $env:programdata\containers\containers.conf.d\99-podman-machine-provider.conf where the machine provider is specified.
The file gets deleted when upgrading to v5.2. As a consequence, after the upgrade, podman will use the default machine provider (WSL), even if the user had selected Hyper-V during v5.1 installation.
Steps to reproduce the issue
Run the windows installer (podman-5.1.1-setup.exe)
Check that the machine provider config file exists
Run a more recent version of the windows installer (i.e. the manually built podman-5.2.0-dev-setup.exe)
Describe the results you received
The machine provider config file is deleted
Describe the results you expected
The machine provider config file should be there.
podman info output
N/A
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered:
Issue Description
On a fresh Podman v5.1 installation, the windows installer creates the file
$env:programdata\containers\containers.conf.d\99-podman-machine-provider.conf
where the machine provider is specified.The file gets deleted when upgrading to v5.2. As a consequence, after the upgrade, podman will use the default machine provider (WSL), even if the user had selected Hyper-V during v5.1 installation.
Steps to reproduce the issue
podman-5.1.1-setup.exe
)podman-5.2.0-dev-setup.exe
)Describe the results you received
The machine provider config file is deleted
Describe the results you expected
The machine provider config file should be there.
podman info output
N/A
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: