"podman machine start" fails to run in ADO Pipeline Job on Windows Self-Hosted Agent about podman HOT 5 OPEN

Does the pipeline user have permissions to use WSL?

from podman.

Yes, when we login as the same user, both WSL and podman commands work.
Could there be an issue in the commands being run as a background service?

from podman.

Same here. Cannot autostart podman at boot:
Error: fork/exec C:\Users\user\AppData\Local\Microsoft\WindowsApps\wsl.exe: The file cannot be accessed by the system.
It runs correctly in normal session but cannot run when started via TaskScheduler or as a service. I tried to start it with nssm.exe as adviced to autorun a docker. When I run two commands:

wsl --exec whoami >log
podman machine start >>log

then I can see that wsl runs correctly (output: user.) but "podman machine start" fails.
WSL version: WSL: 2.2.4.0
Windows Server 2022

from podman.

i have the sane issue

from podman.

I face the same issue trying to run podman machine init using ansible, I also received an error like this
Error: fork/exec C:\Users\myuser\AppData\Local\Microsoft\WindowsApps\wsl.exe: The file cannot be accessed by the system

However the path doesn't exist on the remote windows instance when I rdp into it and check.

The weird thing is RDPing into the machine and running podman machine init manually does not throw an error :P

from podman.