indy-node-container
indy-node-container copied to clipboard
hyperledger
Clarify: node out of consensus
After running the debian based container in the ID Union Test Network for a few days, the node is now out of consensus ("3.0"). Maybe the Pypi package should be replaced by the deb package for indy node 1.12.4, also adressing the missing init script issue https://github.com/IDunion/indy-node-container/issues/3
Just to let you know - I've been running a local test network (4 nodes on the same docker host) for more then 7 days now and I don't see any problems.
update: switching back to an old ubuntu 16 image ultimately resolved the problem, so the Problem DOES seem to be related to our image. https://hackmd.io/GSJnYPt0Q9yFKgoNGWtcMw?view
To me, the most suspicios part are the pypi packages in our image VS the deb packages in the working one. More investigations needed here.
It seems more and more likely, that the current ubuntu 18 and debian images are not in write consensus with the ubuntu 16 node 12.4.3. IFIS has similar problems with the ubuntu 18 node in the IDU networ.
Clarification: :heavy_check_mark:
-> fix images!
Current state (see also https://github.com/IDunion/indy-node-container/issues/38 ): the consensus problems might be related to different libsodium/libssl versions. Sometime a container build with the new libs runs for a while before the consensus problem occurs (happened with the node 1.13 dev ubuntu 20 container in the ID Union test network and before also for the node 1.12.4 debian container).
@Echsecutor - I am running the Ubuntu18 build and running into a consensus issue - should I be moving to the unbuntu20 container or is there a way to confirm that the libs are the correct version in the ubuntu18 build?
@m-madore the Ubuntu18 build uses the same (old) libraries as the Ubuntu16 build - so there shouldn't be any consensus problems. Can you please create an issue with more information and details from the log?