Closed bfan2023 closed 3 months ago
FYI — @reflectivedevelopment @cjhowland @loneil
This is duplicated from issue https://github.com/hyperledger/aries-akrida/issues/49, there is a workaround in there that I use (which is indeed pinning to an earlier Node version). This has been fixed in more up to date Credo libraries.
The workaround described in issue https://github.com/hyperledger/aries-akrida/issues/49 worked for me. Now I see the following issue with the latest 'main' ,
ubuntu@ip-10-0-0-164:~/aries-akrida$ docker-compose -f docker-compose.demo.yml up
WARN[0000] The "NODE_ENV" variable is not set. Defaulting to a blank string.
WARN[0000] The "ISSUER_TYPE" variable is not set. Defaulting to a blank string.
WARN[0000] The "VERIFIER_TYPE" variable is not set. Defaulting to a blank string.
WARN[0000] The "OOB_INVITE" variable is not set. Defaulting to a blank string.
service "mediator-db" refers to undefined volume mediator-db: invalid compose project
the repo on my env FYI,
commit ebf452359741269fccf82f14d2e19e712dedc77a (HEAD -> main, origin/main, origin/HEAD)
Merge: 5f6d0f9 43770e4
Author: Stephen Curran <swcurran@gmail.com>
Date: Mon May 20 16:33:10 2024 -0400
Merge pull request #43 from anwalker293/fix/misc-fixes
Hi @bfan2023 ! Sorry for the late reply, I didn't get any notifications on this issue!
Could you possibly try a git fetch && git pull
? And maybe send over your .env
? It looks like maybe somewhere the mediator
service got labeled to mediator-db
... (If you want to double-check this too, please see our sample.demo.env
! :) )
Hello @anwalker293 , the issue that @bfan2023 mentions is actually due to the faulty Dockerfile. I have fixed the issue in PR: https://github.com/hyperledger/aries-akrida/pull/65. Faced a similar issue myself when trying to have a setup locally.
CC: @loneil @swcurran
I followed the quick start this morning, and everything appears to be working. Please re-open ticket if you are still having issues.
I followed instructions at https://github.com/hyperledger/aries-akrida/blob/main/docs/QUICKSTART.md
After running
docker-compose -f docker-compose.demo.yml up
, I got following errors when=> [load-agent release 4/4] RUN yarn install
. I wonder if recent node 18.20.3 release caused this problem. Because I am able to do 'yarn install' with node 18.18.2 for 'load-agent' on a local directory.=> ERROR [load-agent release 4/4] RUN yarn install 37.7s