Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Don't hardcode host addr to 0.0.0.0 #7

Closed
Luap99 opened this issue Sep 10, 2021 · 0 comments
Closed

Don't hardcode host addr to 0.0.0.0 #7

Luap99 opened this issue Sep 10, 2021 · 0 comments

Comments

@Luap99
Copy link
Member

Luap99 commented Sep 10, 2021

Right now this plugin sets the host addr for gvproxy to 0.0.0.0. This is the default for podman but it can be changed by a user. If you use -p 127.0.0.1:8080:80, gvproxy should only bind 127.0.0.1:8080 in this case. Adding support for this to the plugin is trivial the problem is that in the VM the actual port mapping into the container also tries to use the same host ip. This obviously conflicts, if 127.0.0.1 is also binded in the VM gvproxy cannot reach this addr from the host.

Generally speaking supporting the -p hostaddr:hostport:conport syntax correctly requires a lot of work in this plugin and podman. What needs to happen is that in the VM the host addr part will be ignored and only on the actual remote host applied.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant