Skip to content
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

Container method fails mysteriously when Docker daemon is remote or in a VM #873

ark3 opened this issue Dec 14, 2018 · 1 comment · Fixed by #1128


Copy link

@ark3 ark3 commented Dec 14, 2018

Telepresence should detect this case and report an error rather than crashing after a timeout. A remote daemon (running on another machine) or a daemon running in a VM (such as when using eval $(minikube docker-env)) fail the same way. Maybe we should run something like the network container and check whether we can connect to it. This would also be an opportunity to catch other things that can break launching the network container.


This comment has been minimized.

Copy link
Contributor Author

@ark3 ark3 commented Jun 6, 2019

A fairly quick and easy check is something like

$ docker run --rm --entrypoint "" -v /tmp/tel-xto32c_c:/tel datawire/telepresence-local:0.99 cat /tel/session_id.txt

where /tmp/tel-xto32c_c is runner.temp and the hex blob that comes back should be runner.session_id.

This test will take maybe 1.5 seconds once the image is pulled, and that image pull cost has to be paid anyhow.

@ark3 ark3 moved this from To do to In progress in Tel Tracker Sep 26, 2019
@ark3 ark3 closed this in #1128 Sep 26, 2019
Tel Tracker automation moved this from In progress to Done Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.