[doc] note that run-thirdparties-docker.sh only recognises eth[0-9] NIC names#3755
Merged
morningman merged 1 commit intoMay 24, 2026
Merged
Conversation
…face names The script in `docker/thirdparties/run-thirdparties-docker.sh` detects the primary network interface by grep-ing for `eth[0-9]`. On modern Linux distros that use systemd/udev predictable names (`enp3s0`, `ens33`, `eno1`, …), the detection silently fails and the container set-up cannot start. Add a one-paragraph note to the External Data Source e2e Tests preparation section in EN + zh community guides, telling the reader to set `eth_name` manually when their NIC doesn't match `eth[0-9]`. Fixes apache#3196 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
b3ec868 to
380370b
Compare
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
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
`docker/thirdparties/run-thirdparties-docker.sh` detects the primary NIC by grep-ing for `eth[0-9]`. On modern Linux distros using systemd/udev predictable names (`enp3s0`, `ens33`, `eno1`, …), this silently fails and the container set-up cannot start.
Add a one-paragraph note to the External Data Source e2e Tests › 0. Preparation section in EN + zh community guides, telling the reader to set `eth_name` manually when their NIC doesn't match `eth[0-9]`.
Fixes #3196