update experimental ubuntu20 container to 1.13.2~rc5

[Echsecutor]

Signed-off-by: Sebastian Schmittner sebastian.schmittner@eecc.de

[c2bo]

There seems to be an issue with the tests? https://github.com/hyperledger/indy-node-container/actions/runs/4082605570/jobs/7037223485#step:9:32

{ [112 bytes data]
  * Connection #0 to host localhost left intact
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  jq: error (at ledger_state.json:6): Cannot iterate over null (null)
  Node 1 (synced=, write-consensus=, unreachable-nodes=null): null
  Node 2 (synced=, write-consensus=, unreachable-nodes=null): null
  Node 3 (synced=, write-consensus=, unreachable-nodes=null): null
  Node 4 (synced=, write-consensus=, unreachable-nodes=null): null

[c2bo]

I tried testing locally and the rc5 version seems to work for me. Any ideas how we can debug what exactly is happening with the docker-compose/nodes inside the github worker?

edit: nvm, after pulling all images again (i had old ones) i see similar behavior (even without the rc5 image). My current guess would be a change in the behavior of the ledger-browser? It seems they recently switched to indy-vdr and the output provided by the ledger-browser for /status changed?

[c2bo]

Adding - LEDGER_SEED=000000000000000000000000Steward1 to the docker-compose (webserver) fixes the behavior. I will push to this branch with a fix