-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 commands info, pull and others do not work with Podman 5.0.1 on windows using podman machine #22439
Comments
Is this a dup of #22423? Can you check your system connections? |
@Luap99 Likely not, this is windows. This one is more close to what I am seeing: #22373. Although I decide to open new issue to provide different steps to reproduce. I tried image from 2021-04-09 and it works. |
So this one v20240418122826 is broken. This one works: v20240417162145. |
the latest image had the service down. Let me find image that broke it, I am close. |
Some of these changes broke it:
|
Please show the logs of the service, what is the error? |
|
|
Thanks, this looks bad!
The error message is just missing (empty) for whatever reason, so it impossible to tell what what the real service error cause is. |
The debug level logs are as follows.
|
This is the broken update, it enabled composefs which never should have happen, #22417 There a series of bigger problems here, first podman-next brings in broken rawhide changes. I think @lsm5 works on improving the flow for contianers-common to follow upstream changes with packit like done for our other packages (containers/common#1960) which should hopefully prevent us shipping bad changes like that. Second, why are shipping daily updates from podman-next in our podman-machine WSL images? Shouldn't this be stable and not use development snapshots? And lastly why the hell is no error message being reported, that is some real bug within podman. I still need to debug this. |
c/storage returns empty errors, filled a issue for this: containers/storage#1891 |
I have rolled the stream back to v20240417162145. As soon as there is a fix will pull in the new one and restart updates |
Thanks for the catching this! |
This error also occurs on macos
and
So why is Remark: Increasing the disk size of the VM using dpoman desktop don't fix the problem |
Issue Description
On windows using rootful podman machine, if I try to pull an image:
or
podman info
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Cannot connect to Podman. Please verify your connection to the Linux system using
podman system connection list
, or trypodman machine init
andpodman machine start
to manage a new Linux VMError: unable to connect to Podman socket: Get "http://d/v5.0.1/libpod/_ping": ssh: rejected: connect failed (open failed)
Describe the results you expected
Pulled image.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Windows 10, using wsl as hypervisor.
Additional information
The text was updated successfully, but these errors were encountered: