Mario Loriedo
Mario Loriedo
@danegsta [one test is failing](https://api.cirrus-ci.com/v1/artifact/task/4901695961956352/html/machine-hyperv-podman-windows-rootless-host-sqlite.log.html#t--run-cp-commands-podman-cp--1) on both WSL and Hyper-V: ``` STEP: copy from host to container by name - C:/Users/Administrator/AppData/Local/cirrus-ci-build/repo[/pkg/machine/e2e/cp_test.go:110](https://github.com/containers/podman/blob/24d7eaf6879059239b17ee593015ee1e3cb4aea9/pkg/machine/e2e/cp_test.go#L110) @ 04/08/25 18:32:23.41 C> podman.exe -r cp Z:\ginkgo1275841403\foo.txt podman-cp-test:/tmp/rename.txt...
> There's one failing test, but it seems like it should be a flaky test as I've rebased a couple times and it seems that a different random test fails...
Tests are green. Great job, @danegsta. About your last change: it's usually preferable to use `path/filepath` rather than `path` for manipulating file paths. However container paths must be consistent across...
@jeffmaury Thank you for testing! The problem you get doesn't seem related to the problem this PR is trying to solve. In this case, `machine start` fails with error: >...
When you say same error you mean "key already exist" or "accepts 2 arg(s), received 3"?
Opened a distinct [issue](https://github.com/containers/podman/issues/26021) for the `Error: Illegal argument (key already exists?) (32773)` problem (that is unrelated to this PR).
@containers/podman-maintainers PTAL The tests are green, and we have verified with @jeffmaury that the PR fixes the problem that prevented running HyperV on his laptop.
@mheon I am adding the `5.5` label as it would be nice to include this fix in the next release.
These are different options: `--security-opt label=disable` disables the SELinux labels check, whereas `z` relabel every file object in the volume and can have undesired side effects. There is no option...