Repository navigation
Docker: recommend host networking, document device suggestions - #1203
Merged
Merged
Conversation
andig
reviewed
Oct 3, 2026
naltatis
enabled auto-merge (squash)
October 3, 2026 13:21
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.
fixes #1202, refs evcc-io/evcc#34244
The Docker guide treated bridge networking as the standard and only showed host networking in a tab for SMA devices and EEBus. With device suggestions in the host field, host networking has a further benefit, since a container in bridge mode doesn't see the local network.
docker runcommands broke them, and the host examples published ports that are ignored in host modemachine-idmount,commandandversionremoved from the examples, port 28376/udp for EVSE Master addedEVCC_DISCOVERY_HOSTS, a static device list for controlled bridge setups