-
Notifications
You must be signed in to change notification settings - Fork 763
problem with docker-compose #2430
Comments
Can confirm this is a problem. We really want to use this for an important research project but we cannot seem to get the docker-compose project to function properly and are having exact same issues described by @neginkheirmand Can the developers here give us some indication of what we are doing wrong or perhaps some direction to move forward with? Thanks! |
@neginkheirmand Would you be able to show me exactly how you changed from nightly to latest ( I assumed from yaml) so as to be able to check that peer nodes work (Quote from you: After this change the "sawtooth peer list" and the "curl http://sawtooth-rest-api-default-0:8008/peers" commands work properly.) I haven't been able to get this to work even when changing all from nightly to latest. The error that I keep getting is:
It is my first time venturing into blockchain/sawtooth and docker and I must say that it's very daunting. |
I was facing following transaction error problem just after successfully running following docker file.@jallphin you can re-produce the error after successfully starting following docker file. version: "3.6" volumes: services: ---== shared services ==---sabre-cli: tnt-contract-builder: schema-contract-builder: pike-contract-builder: product-contract-builder: location-contract-builder: validator-0: sawtooth-rest-api1: sawtooth-rest-api2: sawtooth-rest-api4: sawtooth-settings-tp: sabre-tp: sawtooth-client: pbft-1: pbft-2: pbft-3: pbft-4: |
I usually see exactly the same problem, with the exception that, just sometimes, I get COMMITTED from the link then the |
I have been following the documentation to deploy a sawtooth test network (using docker) but failed with both poet and pbft versions.
The nightly tag of docker is outdated and does not work with the docker-compose anymore, however I have been able to deploy the poet version by just changing the tag part of the images in docker-compose from nightly to latest. After this change the "sawtooth peer list" and the "curl http://sawtooth-rest-api-default-0:8008/peers" commands work properly.
Yet when trying to set a key named MyKey to the value 999 according to this command, I run into other problems:
intkey set --url http://sawtooth-rest-api-default-0:8008 MyKey 999
I get the response:
{
"link": "http://sawtooth-rest-api-default-0:8008/batch_statuses?id=8a9cde13ada7bc4f06e6736acf54689515946d8865538544b6e71744a50f861d6621a9e5e94d073b495858116c7c7d5685c6341e65389af30d12bdea78d6b90c"
}
which may seem rational according to the documentation but when I try to run this command:
intkey show --url http://sawtooth-rest-api-default-1:8008 MyKey
I get the following response:
Error: No such key: MyKey
now if I curl the specified link from the response of the intkey set command I get that the status is pending
curl "http://sawtooth-rest-api-default-0:8008/batch_statuses?id=8a9cde13ada7bc4f06e6736acf54689515946d8865538544b6e71744a50f861d6621a9e5e94d073b495858116c7c7d5685c6341e65389af30d12bdea78d6b90c"
the response:
{
"data": [
{
"id": "8a9cde13ada7bc4f06e6736acf54689515946d8865538544b6e71744a50f861d6621a9e5e94d073b495858116c7c7d5685c6341e65389af30d12bdea78d6b90c",
"invalid_transactions": [],
"status": "PENDING"
}
],
"link": "http://sawtooth-rest-api-default-0:8008/batch_statuses?id=8a9cde13ada7bc4f06e6736acf54689515946d8865538544b6e71744a50f861d6621a9e5e94d073b495858116c7c7d5685c6341e65389af30d12bdea78d6b90c"
}
The text was updated successfully, but these errors were encountered: