hutomadotAI / Hutoma-Conversational-AI-Platform

Hu:toma AI is an open source stack designed to help you create compelling conversational interfaces with little effort and above industry accuracy
https://www.hutoma.ai
Apache License 2.0
37 stars 22 forks source link

Can't create an user #23

Open aermike opened 4 years ago

aermike commented 4 years ago

when run ./create_test_user.sh received that ./create_test_user.sh Error: No such container: hutomaoss_api-db_1 Error: No such container: hutomaoss_api-db_1 Error: No such container: hutomaoss_api-db_1 Error: No such container: hutomaoss_api-db_1 with ./launch.sh

aermike commented 4 years ago

here is entire log https://pastebin.com/cjEtEEXS

ghost commented 4 years ago

From the logs the problem seems to be that the containers are being created with a SHA postfix (hutomaoss_api-db_1_a0f7e084b454) instead of just the service name (hutomaoss_api-db_1). Can you provide the docker and docker-compose versions you're using please? (docker --version and docker-compose --version) Thanks.

ghost commented 4 years ago

If you're running docker-compose version 1.23.0 or 1.23.1 you will see this behaviour, which has been fixed from version 1.23.2 on:

Reverted a 1.23.0 change that appended random strings to container names created by docker-compose up, causing addressability issues. Note: Containers created by docker-compose run will continue to use randomly generated names to avoid collisions during parallel runs.

(from https://github.com/docker/compose/releases/tag/1.23.2)

Please update docker-compose to at least 1.23.2, or ideally to the latest version (1.24.1). Thanks.

aermike commented 4 years ago

Hi Sorry for delay

docker --version Docker version 19.03.4, build 9013bf583a

[root@platform]# docker-compose --version docker-compose version 1.23.2, build 1110ad01

ghost commented 4 years ago

Hi, I'm not able to reproduce this behaviour with the latest version of docker-compose (1.24.1), as the service name comes up as expected thus allowing the script to run. You can either update docker-compose to the latest version (recommended) otherwise you can launch the system, run docker ps and check the service name (should be hutomaoss_api-db1< HASH >), then change the _create_testuser.sh script, where it reads DB_IMAGE='hutomaoss_api-db_1' to DB_IMAGE='hutomaoss_api-db_< HASH >' (note the < HASH > should be replaced by whichever value you have). Since you only need to run the script once to create the user, there's no need to further change the script later. Thanks.

aermike commented 4 years ago

Hi I give you the logs tomorrow On Wednesday, October 23, 2019, 1:59:18 PM GMT+3, Pedro Teixeira notifications@github.com wrote:

Hi, I'm not able to reproduce this behaviour with the latest version of docker-compose (1.24.1), as the service name comes up as expected thus allowing the script to run. You can either update docker-compose to the latest version (recommended) otherwise you can launch the system, run docker ps and check the service name (should be hutomaoss_api-db1), then change the create_test_user.sh script, where it reads DB_IMAGE='hutomaoss_api-db_1' to DB_IMAGE='hutomaossapi-db' (note the should be replaced by whichever value you have). Since you only need to run the script once to create the user, there's no need to further change the script later. Thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

aermike commented 4 years ago

Hi Problems is our company filters facebook, and hutoma want tot connect to After testing in other locations it works, but is verry slow I use an VM with 4CPU and 16GB of RAM, 100GB hdd with ssd in back