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

ERROR: No such service: verifier-wallet-db #1

Open
rena2019 opened this issue Oct 5, 2021 · 2 comments
Open

ERROR: No such service: verifier-wallet-db #1

rena2019 opened this issue Oct 5, 2021 · 2 comments

Comments

@rena2019
Copy link

rena2019 commented Oct 5, 2021

After I created the 4 env files with

cp /root/aries-jupyter-playground/playground/issuer/example.env /root/aries-jupyter-playground/playground/issuer/.env
cp /root/aries-jupyter-playground/playground/holder/example.env /root/aries-jupyter-playground/playground/holder/.env
cp /root/aries-jupyter-playground/playground/prover/example.env /root/aries-jupyter-playground/playground/prover/.env
cp /root/aries-jupyter-playground/playground/verifier/example.env /root/aries-jupyter-playground/playground/verifier/.env

I tried to start all with
$ ./manage.sh start
but without luck

Starting up... This can take a couple of minutes.
ERROR: No such service: verifier-wallet-db

What is missing?

@wip-abramson
Copy link
Owner

Hey @rena2019,

I assume this is on branch project/aries-performance?

The issue is the current manage script defines DEFAULT_CONTAINERS with a bunch of verifier-* docker services. Which are not defined in the current docker-compose.yml

Apologies this could definitely be better documented. I was actually running each of these actors in a "production-like" environment on separate VM's. So I was mostly working in the docker-compose.prod.yml file. Let me see if I can push a fix so you can run it locally.

Let me know if you run into further issues. I won't have time to fully test.

Also any P.R's for better documentation either within the notebooks themselves or in a markdown would be always welcome!

@wip-abramson
Copy link
Owner

Okay, it should work now.

Although, I would actually recommend using ./manage production anyway. This basically removes ngrok from the config. Which had problems with rate limiting when I was developing this.

Production should still work with your local environment.

Also note you will need to be running a local von-network - https://github.com/bcgov/von-network

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

2 participants