-
Notifications
You must be signed in to change notification settings - Fork 26
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
WARNING: The MNEMONIC variable is not set. Defaulting to a blank string. #217
Comments
I would like to add here that this only occuers when I start the container directly using docker-compose file .. But when these containers are started using PreTest that time it picks the env variables correctly. i.e. if I run
and picks up correct mnemonics. |
hmm, seems like we probably need to separate the docker compose files so that running a local node is easier. |
I ll let it open so that you can close it, when it done in future releases |
I think I've seen this when starting up a server. Want to see if it's happening, and why it's happening, because the seed should be defined in the configuration file. |
Taking some notes, it looks like this error can be reproduced by running the test for the
So we need to track down where that warning is coming from, and if it's needed or not. |
This should be defaulted to an example. |
When I am starting the docker-compose then the mnemonic does not picked from .env file as mentioned in comment in docker compose file.
and due to that every time, when the container is being restarted a new set of keys are being assigned.
I am starting the container, just by right click on the docker-compose in vscode by selecting "Compose up" option.
The text was updated successfully, but these errors were encountered: