Skip to content
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

Can't create an user #23

Open
aermike opened this issue Oct 18, 2019 · 7 comments
Open

Can't create an user #23

aermike opened this issue Oct 18, 2019 · 7 comments

Comments

@aermike
Copy link

aermike commented Oct 18, 2019

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
Copy link
Author

aermike commented Oct 18, 2019

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

@ghost
Copy link

ghost commented Oct 18, 2019

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
Copy link

ghost commented Oct 18, 2019

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
Copy link
Author

aermike commented Oct 20, 2019

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
Copy link

ghost commented Oct 23, 2019

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-db_1_< HASH >), then change the create_test_user.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
Copy link
Author

aermike commented Oct 23, 2019 via email

@aermike
Copy link
Author

aermike commented Oct 25, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant