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

(enhancement) expose a container port locally while telepresenc-ing #387

Closed
blak3mill3r opened this Issue Dec 22, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@blak3mill3r

blak3mill3r commented Dec 22, 2017

It would be useful to have the option to specify port(s) to expose locally in combination with telepresence's --docker-run option (all other traffic being proxied as usual).

I believe this is currently unsupported (I tried using --docker-run in combination with the --expose or -p options for docker run):

docker: Error response from daemon: conflicting options: port publishing and the container type network mode.

The use case I have in mind is to connect a development tool to a process running in the local telepresenced container.

Specifically: I have a Clojure web service running in a container, if I use telepresence with --docker-run then I am unable to connect a local nREPL client to it. If I use --method=vpn-tcp and run the Clojure process directly on the host, then this is possible, but this is not ideal.

@ark3 ark3 added the enhancement label Dec 26, 2017

@ark3 ark3 closed this in e655d67 Jan 23, 2018

@ark3

This comment has been minimized.

Contributor

ark3 commented Jan 31, 2018

Telepresence release 0.75 includes the fix for this issue. Please take a look and let us know if you run into any trouble. Thanks!

@blak3mill3r

This comment has been minimized.

blak3mill3r commented Feb 7, 2018

Works like a charm. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment