-
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
Cannot create networks using docker-compose when using podman machine on macOS #11413
Comments
@ashley-cui @baude PTAL |
For what it's worth, I got docker-compose working here using largely the approach suggested by #11397 (comment). |
Same problem here in MacOS.
|
Can you paste the output of the file. It looks like it does not contain proper json. |
@Luap99 This is the content of created
|
Yeah the network file looks good. It looks like one of the cni plugins is failing. Can you run the process with strace -f this should show where it fails. |
@Luap99 Since the VM created by |
Ah, I am not a coreos user so I don't know what the best way to install strace or such tools. |
@Luap99 Thank you. It's just as you said removing the In the MacOS host, if I don't use custom network, forward port mapping is working fine.
But with custom network, the port is not forwarded (it works fine inside the podman VM though)
|
Yes the podman-machine plugin sets up the port forwarding, so there is a bug with the plugin. I will see if I can find it. |
I’ve been seeing this “unexpected end of JSON input” error all day yesterday while playing with the latest podman for Mac (after the docker announcement) and I’ve seen it with some rather simple used cases to. I’ll do some testing and report back the images and use cases that fail. Part of the problem is that even with log-level=trace I don’t get any more detail on why the failure happens than the base CLI output. |
Simple example
However, just adding the
Happens in the same manner whether rootless or rootful connection. |
When no ports are set we still have to return the CNI result back. Otherwise CNI will fail with `unexpected end of JSON input`. Fixes containers/podman#11413 Signed-off-by: Paul Holzinger <[email protected]>
TLDR, the bug is that you cannot use the machine plugin without ports. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When creating networks via docker compose, functionality which worked via virtualbox no longer works with
podman machine
.Steps to reproduce the issue:
docker-compose.yml
:docker-compose up
Describe the results you received:
Describe the results you expected:
A working service with a network.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Local MacBook Pro
The text was updated successfully, but these errors were encountered: