Abhay Saxena

Ah. Worst case, you'll have to install Python3 from source. Telepresence requires Python 3.5 or later. Thank you for your help with this.

The Telepresence documentation has a [list of dependencies](https://www.telepresence.io/reference/install.html#dependencies), but it does not explain how to install these dependencies on common platforms. We could use your help to fix this! Can...

The quick workaround is to set the `TELEPRESENCE_REGISTRY` environment variable, which defaults to `datawire`. In your example above, you'd set it to `our.own.docker.registry/whatever/path/datawire`. Let's keep this issue around until we...

That sounds like a DNS loop due to your local cluster. Telepresence is supposed to detect this situation automatically, especially given the context name ("minikube"), but right now those heuristics...

Thinking about this some more, my initial reaction was wrong. This is not a DNS loop, so the `--local-cluster` flag won't help here. I notice now (but missed the first...

It would be great if we could detect this case and report an error.

Thank you for the issue. Yup, this is #723. And thank you for the suggestions. In fact, we can do better. If the original container didn't need root (to bind...

@janosroden That approach requires modifying the root filesystem of the container on startup, before launching sshd. This is in fact what Telepresence used to do, but that caused all sorts...

Telepresence uses SSH because it covers volumes (via sshfs), networking (via sshuttle), and port forwarding. Other solutions (combinations of tools, perhaps) could work too.

@dbazhal That's a good idea! Can you please create an issue requesting that as a new feature? We can work out how to make it happen there. Thank you.