From 75ab3daaa991e7e6c3fff3c6ba8d018b00dfef10 Mon Sep 17 00:00:00 2001 From: Thomas Hallgren Date: Fri, 13 Dec 2024 13:14:39 +0100 Subject: [PATCH] Improve wording in a couple of paragraphs. Signed-off-by: Thomas Hallgren --- blog/2024-12-10-telepresence-2.21.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/blog/2024-12-10-telepresence-2.21.md b/blog/2024-12-10-telepresence-2.21.md index f3002539..3e5a8852 100644 --- a/blog/2024-12-10-telepresence-2.21.md +++ b/blog/2024-12-10-telepresence-2.21.md @@ -63,7 +63,7 @@ First, `telepresence connect` establishes network access to the cluster. Then, ` container's environment and volume mounts available locally, allowing local processes to run, but without receiving intercepted traffic. -The syntax for the ingest and intercept commands are very similar, but while the intercept will target a port to +The syntax for the ingest and the intercept command is very similar, but while the intercept will target a port to intercept (and implicitly a container), the ingest command will target a container directly. There's no conflict when several ingests of the same container, possibly on different workstations, happen @@ -107,9 +107,10 @@ becomes: telepresence docker-run --rm -it jonlabell/network-tools ip route ``` -The command will also ensure that port flags like `--publish`, `--expose` works by circumventing the Docker network -limitation using ephemeral socat containers. It will even enable adding additional `--network` flags by temporarily -adding them to the daemon container. +The command will also ensure that port flags like `--publish`, `--expose` works by circumventing a docker network +limitation otherwise preventing this when a container's network is shared. This is achieved using ephemeral socat +containers. The command will also enable adding additional `--network` flags by temporarily adding them to the daemon +container. The `telpresence intercept/ingest --docker-run` now also leverages this technique.