-
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
No output when using docker run hello-world
on Mac/Windows
#16656
Comments
I have tried this myself (I have docker CE windows containers installed at the same time, providing me docker cli) and it worked fine for me. Where are you getting the docker cli from? |
I'm using the Docker CLI shipped with Docker Desktop. Where did you get yours? |
Docker CE for windows containers. I expect the docker cli for docker desktop is some sort of wrapper around docker cli that works only with docker desktop. If your purpose is for testing out podman desktop while still using "docker", you may be better off setting an alias. However I don't know enough about how docker desktop and podman desktop integrates together, so maybe worth waiting for someone else to chime in. |
@jakegt1, where can I download it? I couldn't find. |
@n1hility PTAL |
will take a look. a brief check shows the data is on the wire. Problem seems to affect mac as well, but not moby on linux, perhaps a bug in specific versions. @rcsilva83 for a workaround you can do |
docker run hello-world
on Windowsdocker run hello-world
on MacWindows
docker run hello-world
on MacWindowsdocker run hello-world
on Mac/Windows
Fix is done but is waiting on a release of gvproxy and merge of a corresponding update PR for the release once created. Tracking issue for the gvproxy release is here: |
@n1hility , a new version with the fix was released: https://github.com/containers/gvisor-tap-vsock/releases/tag/v0.5.0 PS: Happy new year :) |
@rcsilva83 thanks, happy new year! I'll get a PR in updating this soon |
The only thing that’s left on this one is that we need to update the brew formula as part of the bump to 4.4 cc @ashley-cui FYI |
A friendly reminder that this issue had no activity for 30 days. |
I just tested with Podman 4.4.1 on Windows and the problem persists. |
Did it have the new version of gvisor? |
How can I check this? |
Can you go into the machine and check the rpm version? |
The |
given that it's a Windows env, it might be getting gvisor from ubuntu / wsl. Maybe their maintainers need to be pinged about this. |
This issue should be long resolved. The relevant fixed process that contained the gvisor-tap-vsock update is win-sshproxy.exe on the Windows side, and is included / installed by the installer (or if you are doing a manual installation using the client zips, you may want to make sure you have copied all binaries over as part of the install as well). I just doubled checked a clean install of 4.6 and everything looks good there. If this is still happening somehow, feel free to reopen, and any tips on how to reproduce would be appreciated thanks! |
Hi, @n1hility ! Just tested and it is working! Thank you very much for the effort! |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
On Windows, when I run
docker run hello-world
with podman backend, I get no output. If I switch to Docker Desktop backend, I get the correct output.BTW,
podman run hello-world
shows me the output too.Steps to reproduce the issue:
Open a CMD or Powershell
Run
docker run hello-world
Describe the results you received:
Empty output.
Describe the results you expected:
The "Hello from Docker!" message is printed.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Podman installed by Podman Desktop.
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: