Python 3.12 fails to setup on `container` builds

[LecrisUT]

Description:
Interestingly the python setup works fine for the container (Fedora 38) with other versions of python, but the Python 3.12 with allow-prerelease fails for this. Is it that this version is not built for most OS? Is there a workaround for this?

Example run:

Error: The version '3.12' with architecture 'x64' was not found for this operating system.

Action version:
actions/setup-python@v4

Platform:

• Ubuntu (container)
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

[dmitry-shibanov]

Hello @LecrisUT. Thank you for your report. We'll take a look at this issue.

[dmitry-shibanov]

Hello @LecrisUT. Sorry for the late response. I think it is an expected because your container does not have /etc/lsb-release or /etc/os-release that is why the toolkit/tool-cache library can't identify os and its version. You can try to install lsb-release or create /etc/lsb-release file like this

echo -en 'DISTRIB_ID=Ubuntu\nDISTRIB_RELEASE=22.04\nDISTRIB_CODENAME=jammy\nDISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"' >> /etc/lsb-release

After that the action will be able to install python 3.12. For now I'm going to close the issue.

[LecrisUT]

Oh, thanks for the info, I'll fix it on my side.

@dmitry-shibanov , actually the file exits:

$ podman run ghcr.io/lecrisut/dev-env:main cat /etc/os-release
NAME="Fedora Linux"
VERSION="38 (Container Image)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (Container Image)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="Container Image"
VARIANT_ID=container

[dmitry-shibanov]

Hello @LecrisUT. It does not contain DISTRIB_RELEASE that is why I think you need to initialise /etc/lsb-release. After I initialised it the python 3.12 was installed.

[LecrisUT]

@dmitry-shibanov Can you point me to the internal code? I looked to the link you last sent and it contains a check for VERSION_ID which is the ID number for Fedora releases. Note that this is a Fedora container and I do not want to add an ubuntu-like file like that that could affect other CIs.

Do you have any debug runner with more verbose logging that can show where setup-python is failing?

[dmitry-shibanov]

The library tries to get VERSION_ID or DISTRIB_RELEASE to identify Linux version. For python-version DISTRIB_RELEASE is used to identify Linux version that is why you need to specify /etc/lsb-release

[LecrisUT]

That does not explain why only 3.12 is failing, but running with 3.8 which is not bundled in that Fedora image works (See the example run in the first comment). It is the same container that is running all of these actions. I.e. assuming that is the flow, none of my runs should be succeeding. The snippet you've shown using _findMatch would still work without /etc/lsb-release and it would be outputting 38 for comparison.

[dmitry-shibanov]

It works for python 3.8 because it is preinstalled in the hosted toolcache directory. You can try to specify version like 3.11.1 and it will fail.

[LecrisUT]

Indeed specifying the specific version did not work. So then when are the hosted toolcache directories updated? I see that the latest versions are included there since 3.11.4 works. Also I don't think that this would be an appropriate solution if compiler versions differ between ubuntu and fedora. It would be better if there is an option to provide third-party caches for the appropriate container OS.