Version 3.10 with arch x64 not found

Description:
Version 3.10 with arch x64 is not found when running on self-hosted runner.

Action version: latest

Platform:

Ubuntu
macOS
Windows

Runner type:

Hosted
Self-hosted

Tools version:

3.10, altough it seems like all versions are affected

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

- name: Set up Python 3.10
        uses: actions/setup-python@v3
        with:
          python-version: "3.10"
          cache: "pip"

Expected behavior:
Version should be fetched correctly.

Actual behavior:
The 3.10 version for x64 exists but the error says otherwise.

@BlueskyFR

hello @BlueskyFR , can you please provide addional info about the ubuntu version of self-hosted runner?

Sure, it is actually not Ubuntu but Debian Buster

@BlueskyFR

@BlueskyFR while i am reproducing the problem can please try quick solution of the setting AGENT_TOOLSDIRECTORY to /opt/hostedtoolcache (i assume you still use Debian), namely:

- name: Set up Python 3.10
        uses: actions/setup-python@v3
        with:
          python-version: "3.10"
          cache: "pip"
       env:
          AGENT_TOOLSDIRECTORY: /opt/hostedtoolcache

If this helps the original issue should be solved as soon as #394 merged

I am still experiencing the issue. Tried both with the env var mentioned above, and also without

- uses: actions/setup-python@v3
        with:
          python-version: '3.10'
          architecture: 'x64' # optional x64 or x86. Defaults to x64 if not specified
        env:
          AGENT_TOOLSDIRECTORY: /opt/hostedtoolcache

@BlueskyFR

@BlueskyFR @TechDawg270

It is confirmed the problem relates to Debian boosters

Succees on Ubuntu-20
Fail on Debian 10.12

We need a bit more time to investigate the problem with the specific distro

@dsame

@dsame For me it is failing even on Ubuntu-20.04

Description:
Version 3.10 with arch x64 is not found when running on act locally.

Action version: latest

Platform:

Ubuntu

Runner type:

Locally

Tools version:

3.10, although it seems like all versions are affected

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

- name: setup python uses: actions/setup-python@v3.1.2 with: python-version: "3.x" cache: "pip" env: AGENT_TOOLSDIRECTORY: /opt/hostedtoolcache

Expected behaviour:
The version should be fetched correctly.

Actual behaviour:
The 3.10 version for x64 exists but the error says otherwise.

@deepankur797

@deepankur797 , thanks for you input, can you please add the exact step you use to setup python?

I have used the following code in my job


steps:
  -name: setup python
   uses: actions/setup-python@v3
   with:
     python-version: "3.x"
     cache: "pip"
   env:
     AGENT_TOOLSDIRECTORY: /opt/hostedtoolache

@BlueskyFR

@BlueskyFR @TechDawg270

The short story: Debian is not supported, sorry

The only workaround is - either to use Ubuntu for self-hosted machine (any virtualisation works fine) or to install python from the Debian specific repositories.

Long story:
The exact reason is the parsing /etc/os-release and extracting VERSION_ID: while we expect one of "18.04", "20.04" or "22.04" the debian provides "10" and there's no python matched to this version id.

The worst part is we hardly can fix the code because the python from tool cache is built against the libraries specific to the distribution and there's no certainty that the python will work the libraries from the other distribution.

@deepankur797

@deepankur797

The step works without problem on Ubuntu 20.04

      - name: Set up Python 3.10
        uses: actions/setup-python@v3
        with:
          python-version: "3.10"
          architecture: "x64"
        env:
          AGENT_TOOLSDIRECTORY: /opt/hostedtoolcache

Can you please confirm you created opt/hostedtoolcache folder and grant the write permission to the user of the runner on this folder?

@dsame

@dsame thanks for the help it is working now. It was an issue created by some misconfig in the .actrc file as it was using the wrong image. It was overriding the ubuntu image using -P flag.

test: use ubuntu 20.04 instead of latest as the issue in latest (#3608)

Fix ghpages python version string (cartography-cncf#1286)

For me, it fails on Ubuntu oracular. Works on Ubuntu noble.

Hello everyone, The setup-python action supports running Python on GitHub-hosted runners, which are based on Ubuntu, macOS, and Windows environments, as outlined in the documentation. However, certain Linux distributions, such as Debian, are not officially supported. This is because the pre-built Python binaries provided by GitHub Actions are tailored to specific distributions (like Ubuntu) and rely on distribution-specific libraries. As a result, using setup-python on Debian may lead to compatibility issues.

To work around this and support Debian, you can use Ubuntu-based self-hosted runners (virtualization works fine).

Please feel free to reach out if you have any concerns or need further clarification.

Hello Everyone, Please let us know in case of any further concerns/clarifications are needed on the above information

Not caught up on the context here but I am finding this occurs for me when running act to try to run GitHub Actions locally.

I used mise use act to get act:

curl https://mise.run | sh
echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
source ~/.bashrc

I ran this on my repo to run its workflow:

mise use act
act -j linux

[CI/linux-6     ] ⭐ Run Main actions/setup-python@v5
[CI/linux-6     ]   🐳  docker cp src=/home/louis/.cache/act/actions-setup-python@v5/ dst=/var/run/act/actions/actions-setup-python@v5/
[CI/linux-6     ]   🐳  docker exec cmd=[/usr/local/bin/node /var/run/act/actions/actions-setup-python@v5/dist/setup/index.js] user= workdir=
[CI/linux-6     ]   ❓  ::group::Installed versions
| Failed to resolve version 3.10 from manifest
| Version 3.10 was not found in the local cache
[CI/linux-5     ]   ❗  ::error::The version '3.10' with architecture 'x64' was not found for this operating system.%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
[CI/linux-5     ]   ❌  Failure - Main actions/setup-python@v5 [904.328416ms]
[CI/linux-5     ] exitcode '1': failure
[CI/linux-5     ] ⭐ Run Complete job
[CI/linux-5     ]   ✅  Success - Complete job
[CI/linux-5     ] 🏁  Job failed
| Failed to resolve version 3.10 from manifest
| Version 3.10 was not found in the local cache
[CI/linux-6     ]   ❗  ::error::The version '3.10' with architecture 'x64' was not found for this operating system.%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
[CI/linux-6     ]   ❌  Failure - Main actions/setup-python@v5 [847.627548ms]

I am on Linux Mint 22/Wilma (an Ubuntu 24.04/Noble based distro), and am using Ubuntu 22.04/Jammy docker images in the workflow

  linux:
    needs: [check-commit]
    runs-on: ${{ matrix.platform.runner }}
    strategy:
      fail-fast: false
      matrix:
        platform:
          - runner: ubuntu-22.04
            target: x86_64
            before: yum install -y openssl-devel
          - runner: ubuntu-22.04
            target: i686-unknown-linux-gnu
            before: yum install -y openssl-devel.i686
          - runner: ubuntu-22.04
            target: aarch64
          - runner: ubuntu-22.04
            target: armv7
          - runner: ubuntu-22.04
            target: s390x
          - runner: ubuntu-22.04
            target: ppc64le
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: 3.x

@lmmx

Hello @lmmx, Thank you for the issue with detailed logs and as mentioned in the above comments Setup-python action is designed to support GitHub-hosted runners based on Ubuntu, macOS, and Windows environments, as outlined in the official GitHub documentation

However, certain Linux distributions, such as Debian, are not officially supported. This is because the pre-built Python binaries provided by GitHub Actions are tailored to specific distributions (like Ubuntu) and rely on distribution-specific libraries. As a result, using setup-python on Debian may lead to compatibility issues.

Please feel free to reach out if you have any concerns or need further clarification.

Setup-python action is designed to support GitHub-hosted runners based on Ubuntu…

certain Linux distributions, such as Debian, are not officially supported.

using setup-python on Debian may lead to compatibility issues

I am on an Ubuntu-based distro and am using Ubuntu images in Docker, so I am using Ubuntu, not Debian.

I am using Ubuntu 22.04/Jammy docker images running on act which runs the Docker images. I said this.

@lmmx

Hello @lmmx, thank you for the clarification and additional context.
You're right in pointing out that you're using an Ubuntu-based distribution and Ubuntu Docker images with act. However, it's important to note that the setup-python action relies on pre-built binaries and a manifest (versions-manifest.json) tailored specifically for GitHub-hosted runners. These runners have certain environment guarantees (like pre-installed dependencies and directory structures) that act does not fully replicate, even if the Docker image is Ubuntu-based.
In your case, the error:
The version '3.10' with architecture 'x64' was not found for this operating system
indicates that the setup-python action couldn't find a compatible Python binary matching the environment simulated by act. This is a known limitation when running actions locally with act, especially for actions that depend on tightly controlled hosted runner environments like setup-python.
Please feel free to reach out in case further concerns or clarifications are required.

@lmmx

Hello @lmmx, Please let us know in case of any further concerns/clarifications are needed on the above information

it's important to note that the setup-python action relies on pre-built binaries and a manifest (versions-manifest.json) tailored specifically for GitHub-hosted runners.

But you support self-hosted runners (I am unsure why you have posted above the docs about GitHub-hosted runners when both are supported). It sounds almost like you're saying support for self-hosted runners is being dropped, in contradiction to the docs.

The software is meant to run on Ubuntu, but has the bug report of it not doing so, it seems like a bug and so should not have been closed as resolved (which is being justified on the basis that the reports were only for Debian, but then that was extended when also reported on Ubuntu to say that the reports were not on GitHub runners, even when self-hosted runners are meant to be supported too).

These runners have certain environment guarantees (like pre-installed dependencies and directory structures) that act does not fully replicate, even if the Docker image is Ubuntu-based. In your case, the error: The version '3.10' with architecture 'x64' was not found for this operating system indicates that the setup-python action couldn't find a compatible Python binary matching the environment simulated by act.

With respect, this is circular logic and not actionable.

I know it was not found, the point of submitting this error report was to inquire with you, the maintainer of the software emitting the error, as to where precisely in the system the mismatch was occurring. It is typical to receive some assistance in locating the source of the error, you appear to be primarily seeking to declare it unsupported so as to close the issue without resolving the bug report. I am perplexed why supporting the use of this software for local testing before deployment is not a priority for its maintainers, it makes the developer experience significantly worse to not know in advance if your Action logic is sound.

This is a known limitation when running actions locally with act

I see no tracking issue where this has been reported and declared resolved or fair game to just be ignored. I see nothing in the docs warning users not to use it with act. Dismissing this bug report and declaring it "known" without any further info leaves me as a user without a resolution. Perhaps you could share more of what is known about it, perhaps link me to where this has been discussed previously, because this was my first interaction with this bug tracker. Obviously I wouldn't be reporting it if I knew the solution, and it blocked me from developing with the setup-python action.

I looked up the issue here and I find various other reports but it just seems to be users suggesting fixes to each other, not maintainers clarifying what the users are doing wrong. Links in case they help others find the solution in their cases:

Here 2 weeks ago: The version '3.XX' with architecture 'x64' was not found for this operating system. #750 (comment)
Here as recently as January: Error: Version X with arch x64 not found #162
Here last year: The version '3.11.6' with architecture 'x64' was not found for this operating system #913 (comment)
Here in 2023: Error: Version 3.9.11 with arch x64 not found #541

The maintainer previously closed it on this condition:

i am going to close this issue because it seems to be resolved and there's no other comments so far. Feel free to open new issue or reopen this one in case of any problem

So I believe this issue should be reopened.

test: use ubuntu 20.04 instead of latest as the issue in latest (#3608)

Navigation Menu

Repository navigation

Version 3.10 with arch x64 not found #401

24 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Version 3.10 with arch x64 not found #401

Description

Activity

dsame commented on May 5, 2022

BlueskyFR commented on May 5, 2022

dsame commented on May 6, 2022

TechDawg270 commented on May 12, 2022

dsame commented on May 17, 2022

deepankur797 commented on Jun 6, 2022

dsame commented on Jun 7, 2022

deepankur797 commented on Jun 7, 2022

dsame commented on Jun 9, 2022

dsame commented on Jun 9, 2022

deepankur797 commented on Jun 9, 2022

24 remaining items

akuzminsky commented on Mar 24, 2025

v-aparnajyothi-y commented on Apr 7, 2025

v-aparnajyothi-y commented on Apr 28, 2025

lmmx commented on May 4, 2025

v-aparnajyothi-y commented on Jun 4, 2025

lmmx commented on Jun 6, 2025

v-aparnajyothi-y commented on Jul 11, 2025

v-aparnajyothi-y commented on Jul 28, 2025

lmmx commented on Aug 25, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions