Mario Loriedo

### Issue Description An image's build fails on Hyper-V when using additional build context. The same build works fine when using WSL as the machine provider. ```log copier: get: "/test":...

Stop skipping machine volume test on Hyper-V

1

This PR is to re-enable the e2e machine test on volume creation on Hyper-V that was disabled because of #21036. We have to wait for the fix https://github.com/containers/common/pull/2100 to be...

Use the WSL convention for the windows machines default volumes

9

Currently on Windows, volumes are mounted differently based on the provider: - WSL automatically mounts the main drive `C:/` under `/mnt/c` on every Linux VM - For HyperV instead, `podman`...

Returns more than one additional image store

2

Closes #2094

Fix machines failing to start when a volume's path contains spaces

1

~Hyper-V~ Machines failed to start when the path of a volume contained a space. To avoid that we are surrounding the path name with quotation marks before invoking `podman machine...

### Feature request description There are different cases when podman requires elevated mode on Windows: 1. the installer copies files in `C:/Program Files` 2. the installer checks if WSL and...

## Describe the problem In Hyper-V machines, by default, the host `C:\` drive is mounted in `/mnt/c` and accessible from a container using a volume (`podman run -v C:\anysubfolder ...`)....

Automatic installation of WSL fails

2

### Issue Description If WSL isn't installed, and a user tries to run `podman machine init` on Windows, Podman tries to install WSL automatically. This flow is currently broken. ###...