docs(docker/container): warn that host-gateway is firewalled by default on Linux - #1407
Merged
Merged
Conversation
…lt on Linux `extraHosts: ["host.docker.internal:host-gateway"]` resolves fine on Linux and then times out under ufw's default `DEFAULT_INPUT_POLICY="DROP"` — the bridge gateway is a host `INPUT` destination. Document that, and add an example that isn't about host access, since the prop is a general hostname pin. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sz7qnfNGrjV19eTPzKNTy7
Contributor
|
Install the packages built from this commit: Alchemyalchemy bun add https://pkg.ing/alchemy/c6c426c@alchemy.run/better-auth bun add https://pkg.ing/@alchemy.run/better-auth/c6c426c@alchemy.run/cloudflare-runtime bun add https://pkg.ing/@alchemy.run/cloudflare-runtime/c6c426c@alchemy.run/frontend-frameworks bun add https://pkg.ing/@alchemy.run/frontend-frameworks/c6c426c@alchemy.run/node-utils bun add https://pkg.ing/@alchemy.run/node-utils/c6c426c@alchemy.run/pr-package bun add https://pkg.ing/@alchemy.run/pr-package/c6c426c@alchemy.run/floci bun add https://pkg.ing/@alchemy.run/floci/c6c426cDistilled@distilled.cloud/core bun add https://pkg.ing/@distilled.cloud/core/809f3d8@distilled.cloud/aws bun add https://pkg.ing/@distilled.cloud/aws/809f3d8@distilled.cloud/axiom bun add https://pkg.ing/@distilled.cloud/axiom/809f3d8@distilled.cloud/cloudflare bun add https://pkg.ing/@distilled.cloud/cloudflare/809f3d8@distilled.cloud/hetzner bun add https://pkg.ing/@distilled.cloud/hetzner/809f3d8@distilled.cloud/neon bun add https://pkg.ing/@distilled.cloud/neon/809f3d8@distilled.cloud/planetscale bun add https://pkg.ing/@distilled.cloud/planetscale/809f3d8 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1398. The
extraHostsexample it shipped teaches the version that silently fails on Linux.host-gatewayis the Docker bridge gateway (172.17.0.1), so the container's packets land on the host'sINPUTchain. ufw shipsDEFAULT_INPUT_POLICY="DROP", so the hostname resolves and the connection then times out — which reads as an application bug, not a firewall one. This is the same root cause as #1334;sudo ufw allow from 172.16.0.0/12fixes it.Adds that caveat to the
Host Accesssection and theextraHostsfield JSDoc, plus a second example, since the prop is a general hostname pin rather than a host-access knob:Note that
Cloudflare.Containerunderalchemy devis unaffected —DockerLoopback.sidecarLoopbackExtraHost()deliberately maps its alias to127.0.0.1plus a bind-mounted unix socket on Linux, precisely to avoid the bridge IP.Comment-only;
tsc -boutput is byte-identical tomain.