Troubleshooting & Workarounds

Method-specific limitations

General limitations & workarounds

Docker containers

When using --method vpn-tcp or --method inject-tcp a container run via docker run will not inherit the outgoing functionality of the Telepresence shell.
If you want to use Telepresence to proxy a containerized application you should use --method container.

localhost and the pod

localhost and 127.0.0.1 will end up accessing the host machine—the machine where you run telepresence—not the pod.
This can be a problem in cases where you are running multiple containers in a pod and you need your process to access a different container in the same pod.

The solution is to access the pod via its IP, rather than at 127.0.0.1.
You can have the pod IP configured as an environment variable $MY_POD_IP in the Deployment using the Kubernetes Downward API:

EC2

Amazon EC2 instances inside a VPC use a custom DNS setup that resolves internal names. This will prevent Telepresence from working properly. To resolve this issue, override the default name servers, e.g.,