Telepresence
  • Docs
  • Case Studies
  • Community
  • About
  • GitHub
  • Community Slack
Telepresence 2 is now the default version of Telepresence. Learn about the switch from Telepresence v1 to v2
  • Quick start
  • Install Telepresence
    • Install
    • Upgrade
    • Install Traffic Manager with Helm
    • Migrate from legacy Telepresence
  • Core concepts
    • The changing development workflow
    • The developer experience and the inner dev loop
    • Making the remote local: Faster feedback, collaboration and debugging
    • Context propagation
    • Types of intercepts
  • How do I...
    • Intercept a service in your own environment
    • Share dev environments with preview URLs
    • Proxy outbound traffic to my cluster
    • Send requests to an intercepted service
  • Telepresence for Docker
    • What is Telepresence for Docker
    • Install into Docker-Desktop
    • Intercept into a Docker Container
    • Not Working?
  • Technical reference
    • Architecture
    • Client reference
      • login
    • Laptop-side configuration
    • Cluster-side configuration
    • Using Docker for intercepts
    • Running Telepresence in a Docker container
    • Environment variables
    • Intercepts
      • Manually injecting the Traffic Agent
    • Volume mounts
    • RESTful API service
    • DNS resolution
    • RBAC
    • Telepresence and VPNs
    • Networking through Virtual Network Interface
    • Connection Routing
    • Using Telepresence with Linkerd
  • FAQs
  • Troubleshooting
  • Community
  • Release Notes

Troubleshooting

My Container isn't recieving/sending cloud traffic

In the intercepts page is a button labeled "Targetable Containers." These are containers that Telepresence can detect that are configured with both host networking and the TUN device.

Edit this page on GitHub
  • Docs
  • Case Studies
  • About
  • GitHub
  • Slack