fix: gateway nginx DNS runtime-resolve voor native Linux (v1.7.3)#42
Merged
fix: gateway nginx DNS runtime-resolve voor native Linux (v1.7.3)#42
Conversation
Op native Linux Docker faalde nginx bij startup met "host not found in upstream api.kvk.nl" omdat proxy_pass een letterlijke hostname bevatte die bij config parse time werd geresolved. De resolver en set-directive waren al toegevoegd maar de variabele werd niet gebruikt in proxy_pass en de Host-header. Gebruik nu $kvk_upstream zodat nginx DNS via de resolver (127.0.0.11) runtime resolvet. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
$kvk_upstreamvariabele inproxy_passenHostheader zodat nginx DNS via de resolver (127.0.0.11) runtime resolvet in plaats van bij config parse timehost not found in upstream "api.kvk.nl"bij startupContext
De resolver-directive en
set \$kvk_upstream ...waren al aanwezig maar de variabele werd niet gebruikt inproxy_pass, waardoor nginx na envsubst nog steeds een letterlijke hostname zag en die bij startup probeerde te resolven. Op Docker Desktop werkte dit door andere DNS-handling; op native Linux niet.