ChinaJeckXu opened a new issue #9516: URL: https://github.com/apache/dubbo/issues/9516
<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy --> - [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate. ### Environment * Dubbo version: 2.7.14、2.7.15 * Operating System version: Linux Centos7.9 Docker 20.10.5 * Java version: 1.8 ### Steps to reproduce this issue 1. docker container start command：docker run -d --name abc --net=host xxx:xxx 2. In the previous version 2.7.9, the address that dubbo reported to the registry after the container was started was the host IP, such as: [192.168.1.100], this is correct, because the docker start command uses --net=host, However, in the latest version 2.7.14 and 2.7.15, the address reported by dubbo to the registry is the internal IP of the container, such as 172.17.0.1. In this case, in the development environment we usually use, the development machine used by the program developer is Unable to connect to the dubbo service started by the container. Pls. provide [GitHub address] to reproduce this issue. ### Expected Behavior <!-- What do you expect from the above steps？--> ### Actual Behavior <!-- What actually happens? --> If there is an exception, please attach the exception trace: ``` Just put your stack trace here! ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
