When combined with docker service, I found a serious bug.

[lynk-coder]

My docker version 19.03.1, nacos version 1.1.3
When I started my nacos with swarm service, I found that once my nacos node listened on ingress network, although my client could connect to nacos discovery, my configuration could not be automatically updated.
I've tried many times, and there's a problem,
However, when I looked at my mysql, config_info table, the data did change.But my client has not been updated.And after restarting my client, the data still does not change, unless I restart my nacos-server.
Everything returned to normal when I used "--publish mode=host,target=8848,published=8848".

[lynk-coder]

docker service create
--publish 8848:8848
--name nacos
--network=mynet
--replicas 1
--update-parallelism 1
--log-opt max-size=10m
--log-opt max-file=3
--env MODE=standalone
--mount type=bind,source=/nacos/conf/application.properties,destination=/home/nacos/conf/application.properties
--mount type=bind,source=/logs/nacos,destination=/home/nacos/logs
nacos/nacos-server

[lynk-coder]

Why is nobody paying attention? Can you clarify whether this problem is a bug?

[nkorange]

I'm not familiar with docker, I forward your issue to project nacos-docker.

[paderlol]

Why is nobody paying attention? Can you clarify whether this problem is a bug?

Only these things I can't analyze is a nacos error,Can u show me the content of application properties and the nacos error log？
And you can reply me on this issue.

Thanks

[lynk-coder]

Can you give me a contact information? It's a little hard to explain. On 10/31/2019 22:52, pader wrote: Why is nobody paying attention? Can you clarify whether this problem is a bug? Only these things I can't analyze is a nacos error,Can u show me the content of application properties and the nacos error log？ And you can reply me on this issue. Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.