Open dkliban opened 1 year ago
Leaving untriaged, @dkliban will look for the existing dynaconf file issue. I think it was related to the python module "click".
@dkliban the prior issue! https://github.com/pulp/pulpcore/issues/3310
Yeah, those things could be related. Regarding this issue, I'm using:
localhost/oci_env/pulp base 0544cdfddb59
ghcr.io/pulp/pulp-ci-centos latest 58411c36ad1d
and I'm not seeing any traceback when starting the container.
For me, the click
error message disappeared when I updated the pulp-ci-centos
container.
Gonna test with the one that @dkliban pointed out.
And just to confirm:
quay.io/pulp/pulp latest 08639dfc0f94 6 hours ago 2.48 GB
and yes, I'm seeing the error messages.
Maybe some differences in the base of the images?
Need to check on the Containerfile of the pulp-ci-centos
image and the one for our production images.
This should be fixed in dynaconf 3.1.12, when it comes out. https://github.com/dynaconf/dynaconf/issues/853
Since this is duplicated with pulp/pulpcore#3310, should we close it as duplicated?
Version quay.io/pulp/pulp latest 728f8846e816 2 weeks ago 2.18 GB
Describe the bug The following tracebacks are present in the logs when I first start pulp multi service container:
and also a little bit later