Build error on v1.0.5 with rocky8 about docker-migrid HOT 3 CLOSED

Changed along with the other other python3-related PREFER_PY3 and MIG_GIT_BRANCH values in the env files, because explicit values broke at least one of the container distro flavors e.g. because they changed git branch to one not working with chosen python(3) or picked python2 on Rocky9 where unavailable.
Closing here but please reopen if any issues remain.

I changed production.env accordingly assuming you don't use it directly on AU or KU IT sites anyway. You probably still want to consider syncing those changes on to your own env files, however.

from docker-migrid.

It sounds like the python lookup failing when building the PAM module for the openssh+sftpsubsys service. My immediate suspicion it that it could be related to the WITH_PY3=False default in development.yml and rocky8+ transitioning to python3. I guess we should flip the default on if so and maybe in any case because we definitely want all the python3 testing we can get.
Do you have a site to test that assumption easily or should I try to get one running?

from docker-migrid.

It does run on our rocky8 'production' test site using WITH_PY3=True. On podman rather than docker, but I guess that detail is irrelevant here.
I realized that it wasn't much effort to spin up that rocky8 development setup on my laptop, so I just did now and can confirm that I got the same error. Commenting out the development.env WITH_PY3 value to effectively rely on the Dockerfile default (True in rocky8) makes it build again. I'll probably commit that solution in the repo.

from docker-migrid.