Closed WadeBarnes closed 11 months ago
I would expect the plugin install to fail if it was not compatible with the existing version of ACA-Py, but downgrading the ACA-Py version is the wrong thing to do.
The release notes indicate the latest version of the plugin should be used with ACA-Py >=0.9.0
Startup error may have been due to an unsynchronized Redis cluster. I need to try the deployment again.
When building a persistent queue mediator instance using this Dockerfile and overriding the
FROM
to useghcr.io/hyperledger/aries-cloudagent-python:py3.9-0.10.4
, the resulting image contains ACA-Py0.8.2
. The plugin install step unexpectedly downgrades the ACA-Py version.build.log
The resulting image encounters startup errors. This new image was upgrading an existing, working, image.