summaryrefslogtreecommitdiffhomepage
path: root/g3doc
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2020-07-09 09:03:14 -0700
committergVisor bot <gvisor-bot@google.com>2020-07-09 09:04:47 -0700
commit8d2910a04dec5ef2c79034d35fce68e9f414d144 (patch)
tree1e570f51076a18d1e8c79d565b52fc1a8666790b /g3doc
parentc4815af9475cc4680c6d598d9c930de892c98aae (diff)
Explain how to bypass the Docker proxy
Neither myself nor bhaskerh@ can consistently remember how to do this. PiperOrigin-RevId: 320407005
Diffstat (limited to 'g3doc')
-rw-r--r--g3doc/user_guide/debugging.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/g3doc/user_guide/debugging.md b/g3doc/user_guide/debugging.md
index 0525fd5c0..54fdce34f 100644
--- a/g3doc/user_guide/debugging.md
+++ b/g3doc/user_guide/debugging.md
@@ -129,3 +129,13 @@ go tool pprof -top /usr/local/bin/runsc /tmp/cpu.prof
```
[pprof]: https://github.com/google/pprof/blob/master/doc/README.md
+
+### Docker Proxy
+
+When forwarding a port to the container, Docker will likely route traffic
+through the [docker-proxy][]. This proxy may make profiling noisy, so it can be
+helpful to bypass it. Do so by sending traffic directly to the container IP and
+port. e.g., if the `docker0` IP is `192.168.9.1`, the container IP is likely a
+subsequent IP, such as `192.168.9.2`.
+
+[docker-proxy]: https://windsock.io/the-docker-proxy/