Closed benibr closed 5 months ago
Yes, I've seen similar when forcing python3
on edge
. Please note that python3
strictly requires the git experimental
branch to build/run.
It probably started showing in relation to the recent changes in Dockerfile
regarding automatic selection of preferred python and git branch to support building each of the different centos and rocky flavors without adjusting the provided development.env
and production.env
files accordingly.
A valid MIG_GIT_BRANCH
and PREFER_PYTHON3
combo should now automatically get selected when left unset in your .env
like in the sample envs. So please leave them both alone or explicitly set PREFER_PYTHON3=False
if you set MIG_GIT_BRANCH=edge
.
Does that help or can you elaborate on the env settings?
I suppose this issue really belongs at docker-migrid
, but if we're looking at the plain migrid
setup the cause is correspondingly the use of prefer_python3=True
with a branch other than experimental
.
Ah okay that makes sense and would explain why the behaviour recently changed. I sometime deployed master
for some testing but then I make sure that I also use always experimental for this.
Anyway, might be good to have this error message archived here, but I guess we can close this issue.
I'm running in a strange new error with current master branch when generateconf.py is called by Docker build
The certs exists and havn't been changed since last deployment. It works with
experimental
branch so it might be a Python related error.