Closed IBMRob closed 3 months ago
Just a first guess, can you try with fips mode disabled in vm.args?
Looks like if fips is disabled then it does start up so the problem is associated with fips being enabled
I think it would be good to report this directly to the Erlang/OTP Team to debug this further regarding fips mode.
There may be a related issue in OTP https://github.com/erlang/otp/issues/8562
There may be a related issue in OTP erlang/otp#8562
That does look very similar
Closing this for now, it seems it's an Erlang/OTP error.
Description
We had a working pair of builds which was producing couchdb images that worked without issue. Due to
https://repo.hex.pm/builds/elixir/v1.17.2-otp-24.zip
being removed we had to upgrade toerlangversion=25.3.2.13
. After this our builder image all builds successfully and then our couchDb image builds sucessfully but when we try and start our couchdb container its throwing the following errors on startupUsing an old image works so we have confirmed its not due to any other changes.
Steps to Reproduce
This is a custom couchdb image so its hard to provide re-create steps although we are essentially based around the same
couchdb-ci
andcouchdb
reposThe main non standard configuration we have is that we have CouchDB configured with TLS
The certs we use are generated by Openshift via the service annotation certificate mechanism -
service.alpha.openshift.io/serving-cert-secret-name
Expected Behaviour
cluster starts and setup can be completed on it.
Your Environment
We see this on our amd64, s390x and ppc64le builds
Output of root
Config
ubi8/ubi-minimal
image.Additional Context