From a478188b483d85cf06ddad5f39067957b872a22e Mon Sep 17 00:00:00 2001 From: Tedi Mitiku Date: Thu, 11 Jul 2024 11:22:45 -0400 Subject: [PATCH] simplify a little bit --- .../advanced-concepts/public-and-private-ips-and-ports.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/docs/advanced-concepts/public-and-private-ips-and-ports.md b/docs/docs/advanced-concepts/public-and-private-ips-and-ports.md index e7e13ae602..84814be3bf 100644 --- a/docs/docs/advanced-concepts/public-and-private-ips-and-ports.md +++ b/docs/docs/advanced-concepts/public-and-private-ips-and-ports.md @@ -45,6 +45,4 @@ The combination of public IP + port _will_ allow you to connect to a container f ### Gotchas -When exposing a port on a `ServiceConfig` via the `ports` field, the container responsible for managing the enclave, APIContainer (APIC), will perform an availability check (`nc -vz `) to ensure the port is exposed. -Some services by default expose ports on `localhost:` or `127.0.0.1:`. This would cause the availability check (eg. `nc -vz 172.0.0.3 9612`) to fail as the APIC communicates with the service on a subnetwork created by Kurtosis for that enclave, -whilst the port is only exposed on the localhost network interface. The workaround is to expose the port on all network interfaces via `0.0.0.0` eg. `--rpc.laddr tcp://0.0.0.0:36657`. \ No newline at end of file +When you expose a port on a `ServiceConfig` via the `ports` field, the container responsible for managing the enclave, APIContainer (APIC), will perform an availability check (`nc -vz `) on the port. Some services default to exposing ports on `localhost:` or `127.0.0.1:`. This causes the availability check (eg. `nc -vz 172.0.0.3 9612`) to fail, as the APIC communicates with the service on a subnetwork created by Kurtosis for that enclave, whilst the port is only exposed on the localhost network interface. The workaround is to expose the port on all network interfaces via `0.0.0.0` eg. `--rpc.laddr tcp://0.0.0.0:36657`. \ No newline at end of file