"host" network mode is incompatible with port binding. The port binding example also shows a restriction to just accepting connections from localhost, which I don't think we want if the encoder is across the network and not running on the same machine that the wg-encoder agent is running.
Motivation and Context
The daq-satp3 deployment configs used this combination "host" mode and port binding, which was preventing the wg-encoder agent container from coming online.
How Has This Been Tested?
The satp1 and satp3 configs have been updated to use just the non-localhost port binding, with no 'host' network mode.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist:
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
Description
"host" network mode is incompatible with port binding. The port binding example also shows a restriction to just accepting connections from localhost, which I don't think we want if the encoder is across the network and not running on the same machine that the wg-encoder agent is running.
Motivation and Context
The daq-satp3 deployment configs used this combination "host" mode and port binding, which was preventing the wg-encoder agent container from coming online.
How Has This Been Tested?
The satp1 and satp3 configs have been updated to use just the non-
localhostport binding, with no 'host' network mode.Types of changes
Checklist: