-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman from WSL not found #1651
Comments
Looks similar to dotnet/aspire#5571. Unable to find an executable on the path. I wonder if this is to do with where the apphost was launched from. |
Thank you! Adding some more context of the terminal environment below, just in case it helps. I have also verified that copying
|
Unfortanetly you can't alias the command to be resovled correctly, podman will need to be part of the environment path. |
At the risk of being a pain, this means Aspire is unusable under the Podman installation instructions at https://podman-desktop.io/docs/podman/accessing-podman-from-another-wsl-instance I’m guessing this is not an isolated case, so if it will not be supported I guess it needs to be documented |
Let's add this to the docs for now. |
Is there an existing issue for this?
Describe the bug
Environment setup:
alias podman='podman-remote-static-linux_amd64'
podman images
runs successfullyError encountered:
: Container runtime 'podman' could not be found. The error from the container runtime check was: exec: "podman": executable file not found in $PATH
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: