Kevin Hu
Kevin Hu
Get into the container and find the right ES IP, then, configure it in service_conf.ymal This is my suggestion.
'http://192.168.2.2:9200/' This is the address outside of the docker container, I guess. In docker envirement, it has it's own network. Good luck!
You could ignore the warning log. And in latest code and image, I've already remove the default redis configuration so the message will not show again.
We are gona fix it.
Upgrade to the latest dev version of the docker image. Problem solved for new knowledgebases. But the former data is still there.
Is it locally deployed? If it is, upgrade it.  docker ps make sure the Redis is up.
Supper fantastic! Appreciate for your contribution! A concern: if the name 'process_duation' is refined, how to update it to the existing users easily and smoothly, who have already deployed locally?...
> > Supper fantastic! Appreciate for your contribution! A concern: if the name 'process_duation' is refined, how to update it to the existing users easily and smoothly, who have already...
Upgrade to the latest dev version of the docker image. Problem solved.
Are your machine Arm64 architecture ?