Adjustable machine proxy port #11728
Assignees
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
machine
Comments
|
I think containers/gvisor-tap-vsock#46 should fix the problem. With this we would not need bind a port at all. |
|
A friendly reminder that this issue had no activity for 30 days. |
|
@Luap99 since this is merged can we close this issue, or is there a change required in Podman? |
|
It needs to be changed in podman as well |
|
@Luap99 Could you make the change in Podman to complete it. |
This was referenced Nov 6, 2021
Luap99
added
the
In Progress
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Nov 15, 2021
This commits adds port forwarding logic directly into podman. The podman-machine cni plugin is no longer needed. The following new features are supported: - works with cni, netavark and slirp4netns - ports can use the hostIP to bind instead of hard coding 0.0.0.0 - gvproxy no longer listens on 0.0.0.0:7777 (requires a new gvproxy version) - support the udp protocol With this we no longer need podman-machine-cni and should remove it from the packaging. There is also a change to make sure we are backwards compatible with old config which include this plugin. Fixes containers#11528 Fixes containers#11728 [NO NEW TESTS NEEDED] We have no podman machine test at the moment. Please test this manually on your system. Signed-off-by: Paul Holzinger <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Maybe this can be adjustable? In my env, I have already an daemon service listen on 7777, so there will be error
podman/pkg/machine/qemu/machine.go
Line 646 in 1dba601
The text was updated successfully, but these errors were encountered: