We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I clone quorum-maker repository (syneblock/quorum-maker:2.2.1_2.6.2)
I run the following commands ./setup.sh dev -p testchain -n 3 -e cd testchain docker-compose up -d
./setup.sh dev -p testchain -n 3 -e
cd testchain
docker-compose up -d
I check the quorum-maker dashboard, all looks good.
then I stop the network with the following command docker-compose down
docker-compose down
when I bring the network up with docker-compose up -d, I see all transactions concatenated into one block on the dashboard.
I tried to docker commit each node's container to an image and docker compose up from those but the result is the same.
docker commit
Do you have any idea how to review the network properly?
The text was updated successfully, but these errors were encountered:
We are actively looking into this problem. Will get back to you soon.
Sorry, something went wrong.
We found a solution and seems to be working. The fixes are pushed to same branch. Can you try again?
Works great, thank you very much.
No branches or pull requests
I clone quorum-maker repository (syneblock/quorum-maker:2.2.1_2.6.2)
I run the following commands
./setup.sh dev -p testchain -n 3 -e
cd testchain
docker-compose up -d
I check the quorum-maker dashboard, all looks good.
then I stop the network with the following command
docker-compose down
when I bring the network up with
docker-compose up -d
, I see all transactions concatenated into one block on the dashboard.I tried to
docker commit
each node's container to an image and docker compose up from those but the result is the same.Do you have any idea how to review the network properly?
The text was updated successfully, but these errors were encountered: