zhquan
commented
1 year ago Hi @roddds
The latest stable version is grimoirelab/grimoirelab:0.7.1. Could you try this version instead?
I guess you are using this docker-compose.yml
Open roddds opened 1 year ago
zhquan
commented
1 year ago Hi @roddds
The latest stable version is grimoirelab/grimoirelab:0.7.1. Could you try this version instead?
I guess you are using this docker-compose.yml
Rafaeltheraven
commented
1 year ago I've been running into this exact same issue. I think it's because the example setup.cfg in this repository has the sortinghat.host key set to mariadb, suggesting that these are the mysql credentials. However, sirmordred is actually using this value to attempt to connect to the sortinghat server, which AFAIK is being hosted by the hatstall image, so the host should be set to hatstall. Having done this, Mordred no longer crashes, but I think there needs to be a bit more tweaking because I don't think the identities phase properly runs.
Rafaeltheraven
commented
1 year ago Right, I think I figured it out.
The issue is that sortinghat has moved over to a service-based architecture, but this repository does not properly reflect that yet.
My relevant modifications to the docker-compose are as follows:
services:
mariadb:
image: mariadb:10.6
expose:
- "3306"
environment:
- MYSQL_ROOT_PASSWORD=
- MYSQL_ALLOW_EMPTY_PASSWORD=yes
healthcheck:
test: ["CMD", "/usr/local/bin/healthcheck.sh", "--su=root", "--connect", "--innodb_initialized"]
redisdb:
image: redis:latest
ports:
- 6379:6379
healthcheck:
test: [ "CMD", "redis-cli", "--raw", "incr", "ping" ]
sortinghat:
image: grimoirelab/sortinghat
environment:
- SORTINGHAT_SECRET_KEY=secret
- SORTINGHAT_DB_HOST=mariadb
- SORTINGHAT_REDIS_HOST=redisdb
- SORTINGHAT_SUPERUSER_USERNAME=root
- SORTINGHAT_SUPERUSER_PASSWORD=root
- SORTINGHAT_DB_DATABASE=sortinghat_db
- SORTINGHAT_HTTP_DEV=0.0.0.0:8000
- SORTINGHAT_ALLOWED_HOST=sortinghat,.localhost,127.0.0.1,[::1]
- DEV_FLAG=1
ports:
- 8000:8000
- 9314:9314
depends_on:
mariadb:
condition: service_healthy
redisdb:
condition: service_healthy
sortinghat_worker:
image: grimoirelab/sortinghat-worker
environment:
- SORTINGHAT_SECRET_KEY=secret
- SORTINGHAT_DB_HOST=mariadb
- SORTINGHAT_REDIS_HOST=redisdb
depends_on:
- sortinghatThen, also modify the setup.cfg so the sortinghat config looks like this:
[sortinghat]
host = sortinghat
user = root
password = root
port = 8000
path = api/
ssl = false
database = sortinghat_db
load_orgs = true
orgs_file = /home/bitergia/organizations.json
autoprofile = [github, pipermail, git]
matching = [email,username]
sleep_for = 100
unaffiliated_group = Unknown
affiliate = true
strict_mapping = false
reset_on_load = false
identities_file = [/home/bitergia/conf/identities.yml]
identities_format = grimoirelabIdeally, there would be an nginx/apache/whatever container acting as a proxy for sortinghat:9314 but to keep it simple, I'm using the dev http server here, which runs on 8000.
zhquan
commented
1 year ago Hi @Rafaeltheraven
The latest stable version (grimoirelab/grimoirelab:0.7.1) does not need sortinghat and sortinghat_worker containers, only need MariaDB.
We are preparing significant changes for the next release (0.8.0), including the new SortingHat (sortinghat and sortinghat-worker). We will add sortinghat sections on the docker-compose/docker-compose.yml and update the default-grimoirelab-settings/setup.cfg when the 0.8.0 release is ready.
I guess you are using grimoirelab/grimoirelab:latest and it needs sortinghat and sortinghat_worker containers but the latest version is not stable and it still has some bugs.
Could you try this docker-compose but using grimoirelab/grimoirelab:0.7.1 instead of grimoirelab/grimoirelab:latest?
yangzhangs
commented
1 year ago I also encountered this problem. I changed the tag and everything did appear to start up normal. Great!
Hi @roddds
The latest stable version is
grimoirelab/grimoirelab:0.7.1. Could you try this version instead?I guess you are using this docker-compose.yml
Rafaeltheraven
commented
1 year ago grimoirelab:0.7.1 works, though the compose file in this repository still uses latest.
As for me, I'm using the latest version of Mordred for my own reasons, so I kinda need latest in a sense. Anyhow, if anybody else wants to use the latest version, they can tentatively use the docker-compose I described.
mykaul
commented
1 year ago Generally, I'm not sure using 'latest' is a good idea - it doesn't give a consistent experience for users.
Waiting for 0.8.0 with a fixed yml..
Apologies if I'm missing any critical debug information. No files in the repository have been changed. The interrupted stack traces at the end continue indefinitely, several times per second. I checked out the most recent release tag, 0.7.2, and got the same results: