-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add subnet setting for Proxy user #7
base: master
Are you sure you want to change the base?
Conversation
@fhueske , |
@fhueske @alpinegizmo @knaufk @rmetzger |
Thanks for the PR @tsjsdbd and sorry for the delay. |
@tsjsdbd I think this issue doesn't affect that many people, and picking another arbitrary IP range (like Have you tried setting the |
@patricklucas I realize that default CIDR using |
By default, Docker use `172.17.0.0/16` to `docker0` interface. like: ``` docker0 Link encap:Ethernet HWaddr 02:42:91:7b:0f:21 inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 ``` and by default, Docker-compose will use `172.18.0.0/16`, `172.19.0.0/16` ...and so on, to new Bridge, like: ``` br-c401dc9ce9fd Link encap:Ethernet HWaddr 02:42:ac:c9:28:9e inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0 ``` But, My environment have proxy endpoint: `172.18.22.221`, if can not setting subnet of docker-compose, the default subnet adderess will conflict with my Proxy, which cause it can not work. so, add subnet setting is meaningful for Proxy user : )
Can you share the metadata? |
* M1 fix again * export STATS_COMPUTE_INTERVAL_MINUTES env
By default, Docker use
172.17.0.0/16
todocker0
interface. like:and by default, Docker-compose will use
172.18.0.0/16
,172.19.0.0/16
...and so on, to new Bridge, like:But, My environment have proxy endpoint:
172.18.22.221
, if can not setting subnet of docker-compose, the default subnet adderess will conflict with my Proxy, which cause it can not work.so, add subnet setting is meaningful for Proxy user : )