[GH-ISSUE #251 ] Unable to execute actions/setup-python #174

Author

Owner

@svdgraaf commented on GitHub (May 20, 2020):

I've hit the same issue, I've found that if you set a GITHUB_TOKEN env var, it doesn't give the bad credentials error, and proceeds, only to fail a bit later:

$ GITHUB_TOKEN=foobar act
...
[tests.yml/tests]   ❗  ::error::Version 3.8 with arch x64 not found%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json
[tests.yml/tests]   ❌  Failure - Setup Python

@svdgraaf commented on GitHub (May 20, 2020): I've hit the same issue, I've found that if you set a `GITHUB_TOKEN` env var, it doesn't give the bad credentials error, and proceeds, only to fail a bit later: ``` $ GITHUB_TOKEN=foobar act ... [tests.yml/tests] ❗ ::error::Version 3.8 with arch x64 not found%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json [tests.yml/tests] ❌ Failure - Setup Python ```

kerem commented

Author

Owner

@svdgraaf commented on GitHub (May 20, 2020):

I'm not sure, but I think it fails because I'm running it on osx, but the installation is running through the docker container on linux, and it's not understanding which version it should install. I think? :)

The manifest does contain the right version it should use: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json

[tests.yml/tests]   💬  ::debug::Semantic version spec of 3.8.3 is 3.8.3
[tests.yml/tests]   💬  ::debug::isExplicit: 3.8.3
[tests.yml/tests]   💬  ::debug::explicit? true
[tests.yml/tests]   💬  ::debug::checking cache: /opt/hostedtoolcache/Python/3.8.3/x64
[tests.yml/tests]   💬  ::debug::not found
| Version 3.8.3 was not found in the local cache
[tests.yml/tests]   💬  ::debug::check 3.8.3 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::x64===x64 && darwin===linux
[tests.yml/tests]   💬  ::debug::x64===x64 && darwin===linux
[tests.yml/tests]   💬  ::debug::x64===x64 && linux===linux
[tests.yml/tests]   💬  ::debug::x64===x64 && linux===linux
[tests.yml/tests]   💬  ::debug::x64===x64 && win32===linux
[tests.yml/tests]   💬  ::debug::x86===x64 && win32===linux
[tests.yml/tests]   💬  ::debug::check 3.8.2 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.8.1 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.8.0 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.7.7 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.7.6 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.7.5 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.6.10 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.6.9 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.6.8 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.6.7 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.5.9 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 3.5.4 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 2.7.18 satisfies 3.8.3
[tests.yml/tests]   💬  ::debug::check 2.7.17 satisfies 3.8.3
[tests.yml/tests]   ❗  ::error::Version 3.8.3 with arch x64 not found%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json
[tests.yml/tests]   ❌  Failure - Setup Python
DEBU[0003] exit with `FAILURE`: 1```

@svdgraaf commented on GitHub (May 20, 2020): I'm not sure, but I think it fails because I'm running it on osx, but the installation is running through the docker container on linux, and it's not understanding which version it should install. I think? :) The manifest does contain the right version it should use: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json ```[tests.yml/tests] Exec command '[node /actions/actions-setup-python@master/dist/index.js]' [tests.yml/tests] 💬 ::debug::Semantic version spec of 3.8.3 is 3.8.3 [tests.yml/tests] 💬 ::debug::isExplicit: 3.8.3 [tests.yml/tests] 💬 ::debug::explicit? true [tests.yml/tests] 💬 ::debug::checking cache: /opt/hostedtoolcache/Python/3.8.3/x64 [tests.yml/tests] 💬 ::debug::not found | Version 3.8.3 was not found in the local cache [tests.yml/tests] 💬 ::debug::check 3.8.3 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::x64===x64 && darwin===linux [tests.yml/tests] 💬 ::debug::x64===x64 && darwin===linux [tests.yml/tests] 💬 ::debug::x64===x64 && linux===linux [tests.yml/tests] 💬 ::debug::x64===x64 && linux===linux [tests.yml/tests] 💬 ::debug::x64===x64 && win32===linux [tests.yml/tests] 💬 ::debug::x86===x64 && win32===linux [tests.yml/tests] 💬 ::debug::check 3.8.2 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.8.1 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.8.0 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.7.7 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.7.6 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.7.5 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.6.10 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.6.9 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.6.8 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.6.7 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.5.9 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 3.5.4 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 2.7.18 satisfies 3.8.3 [tests.yml/tests] 💬 ::debug::check 2.7.17 satisfies 3.8.3 [tests.yml/tests] ❗ ::error::Version 3.8.3 with arch x64 not found%0AThe list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json [tests.yml/tests] ❌ Failure - Setup Python DEBU[0003] exit with `FAILURE`: 1```

kerem commented

Author

Owner

@rgarrigue commented on GitHub (May 20, 2020):

For the records I'm running it under Ubuntu 19.10

@rgarrigue commented on GitHub (May 20, 2020): For the records I'm running it under Ubuntu 19.10

kerem commented

Author

Owner

@whettie commented on GitHub (May 21, 2020):

So good.

@whettie commented on GitHub (May 21, 2020): So good.

kerem commented

Author

Owner

@RaulBSantos commented on GitHub (May 21, 2020):

Same here, and I'm using ElementaryOS under Ubuntu 18.04.4.

Some of you guys tried with another image? Just wondering if this may solve, cause I couldn't try with the alternative image, my disk space it's insufficient :(

@RaulBSantos commented on GitHub (May 21, 2020): Same here, and I'm using ElementaryOS under Ubuntu 18.04.4. Some of you guys tried with another image? Just wondering if this may solve, cause I couldn't try with the [alternative image](https://github.com/nektos/act#alternative-runner-images), my disk space it's insufficient :(

kerem commented

Author

Owner

@rgarrigue commented on GitHub (May 25, 2020):

@RaulBSantos it does work running

act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04

...
[Tests/tests] ⭐  Run Setup Python
[Tests/tests]   ☁  git clone 'https://github.com/actions/setup-python' # ref=v2
[Tests/tests]   🐳  docker cp src=/home/remy/.cache/act/actions-setup-python@v2 dst=/actions/
[Tests/tests]   💬  ::debug::Semantic version spec of 3.7 is 3.7
[Tests/tests]   💬  ::debug::isExplicit: 
[Tests/tests]   💬  ::debug::explicit? false
[Tests/tests]   💬  ::debug::isExplicit: 2.7.17
[Tests/tests]   💬  ::debug::explicit? true
[Tests/tests]   💬  ::debug::isExplicit: 3.5.9
[Tests/tests]   💬  ::debug::explicit? true
[Tests/tests]   💬  ::debug::isExplicit: 3.6.10
[Tests/tests]   💬  ::debug::explicit? true
[Tests/tests]   💬  ::debug::isExplicit: 3.7.6
[Tests/tests]   💬  ::debug::explicit? true
[Tests/tests]   💬  ::debug::isExplicit: 3.8.1
[Tests/tests]   💬  ::debug::explicit? true
[Tests/tests]   💬  ::debug::evaluating 5 versions
[Tests/tests]   💬  ::debug::matched: 3.7.6
[Tests/tests]   💬  ::debug::checking cache: /opt/hostedtoolcache/Python/3.7.6/x64
[Tests/tests]   💬  ::debug::Found tool in cache Python 3.7.6 x64
[Tests/tests]   ⚙  ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.7.6/x64
[Tests/tests]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64
[Tests/tests]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64/bin
[Tests/tests]   ⚙  ::set-output:: python-version=3.7.6
| Successfully setup CPython (3.7.6)
[Tests/tests]   ❓  ##[add-matcher]/actions/actions-setup-python@v2/.github/python.json
[Tests/tests]   ✅  Success - Setup Python
...

Since that's fine enought for me I'll add the -P option to my .actrc.

For other user willing to push the investigation, the setup-python author suggested following this guideline https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner. I gave it a quick shot without success.

@rgarrigue commented on GitHub (May 25, 2020): @RaulBSantos it does work running ``` act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 ... [Tests/tests] ⭐ Run Setup Python [Tests/tests] ☁ git clone 'https://github.com/actions/setup-python' # ref=v2 [Tests/tests] 🐳 docker cp src=/home/remy/.cache/act/actions-setup-python@v2 dst=/actions/ [Tests/tests] 💬 ::debug::Semantic version spec of 3.7 is 3.7 [Tests/tests] 💬 ::debug::isExplicit: [Tests/tests] 💬 ::debug::explicit? false [Tests/tests] 💬 ::debug::isExplicit: 2.7.17 [Tests/tests] 💬 ::debug::explicit? true [Tests/tests] 💬 ::debug::isExplicit: 3.5.9 [Tests/tests] 💬 ::debug::explicit? true [Tests/tests] 💬 ::debug::isExplicit: 3.6.10 [Tests/tests] 💬 ::debug::explicit? true [Tests/tests] 💬 ::debug::isExplicit: 3.7.6 [Tests/tests] 💬 ::debug::explicit? true [Tests/tests] 💬 ::debug::isExplicit: 3.8.1 [Tests/tests] 💬 ::debug::explicit? true [Tests/tests] 💬 ::debug::evaluating 5 versions [Tests/tests] 💬 ::debug::matched: 3.7.6 [Tests/tests] 💬 ::debug::checking cache: /opt/hostedtoolcache/Python/3.7.6/x64 [Tests/tests] 💬 ::debug::Found tool in cache Python 3.7.6 x64 [Tests/tests] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.7.6/x64 [Tests/tests] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64 [Tests/tests] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64/bin [Tests/tests] ⚙ ::set-output:: python-version=3.7.6 | Successfully setup CPython (3.7.6) [Tests/tests] ❓ ##[add-matcher]/actions/actions-setup-python@v2/.github/python.json [Tests/tests] ✅ Success - Setup Python ... ``` Since that's fine enought for me I'll add the -P option to my .actrc. For other user willing to push the investigation, the setup-python author suggested following this guideline https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner. I gave it a quick shot without success.

kerem commented

Author

Owner

@april commented on GitHub (Jun 12, 2020):

Yep, I'm having the exact same problem here as well. On macOS, always gives me the the Version ... with arch x64 not found error, even if I specify something as specific as 3.8.3.

Setting the .actrc as specified above did fix things, however.

@april commented on GitHub (Jun 12, 2020): Yep, I'm having the exact same problem here as well. On macOS, always gives me the the `Version ... with arch x64 not found` error, even if I specify something as specific as `3.8.3`. Setting the `.actrc` as specified above did fix things, however.

kerem commented

Author

Owner

@grische commented on GitHub (Jun 18, 2020):

I created a simple test file which re-creates the problem

name: pull_requests
on: [pull_request]

jobs:
  test_pr:
    runs-on: ubuntu-18.04
    steps:
      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: "3.7"

It is fixed by adding the -P parameter like the following:

$ act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04 pull_request
[pull_requests/test_pr] 🚀  Start image=nektos/act-environments-ubuntu:18.04
[pull_requests/test_pr]   🐳  docker run image=nektos/act-environments-ubuntu:18.04 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[pull_requests/test_pr] ⭐   Run Set up Python
[pull_requests/test_pr]   ☁  git clone 'https://github.com/actions/setup-python' # ref=v2
[pull_requests/test_pr]   🐳  docker cp src=/home/user/.cache/act/actions-setup-python@v2 dst=/actions/
[pull_requests/test_pr]   💬  ::debug::Semantic version spec of 3.7 is 3.7
[pull_requests/test_pr]   💬  ::debug::isExplicit:
[pull_requests/test_pr]   💬  ::debug::explicit? false
[pull_requests/test_pr]   💬  ::debug::isExplicit: 2.7.17
[pull_requests/test_pr]   💬  ::debug::explicit? true
[pull_requests/test_pr]   💬  ::debug::isExplicit: 3.5.9
[pull_requests/test_pr]   💬  ::debug::explicit? true
[pull_requests/test_pr]   💬  ::debug::isExplicit: 3.6.10
[pull_requests/test_pr]   💬  ::debug::explicit? true
[pull_requests/test_pr]   💬  ::debug::isExplicit: 3.7.6
[pull_requests/test_pr]   💬  ::debug::explicit? true
[pull_requests/test_pr]   💬  ::debug::isExplicit: 3.8.1
[pull_requests/test_pr]   💬  ::debug::explicit? true
[pull_requests/test_pr]   💬  ::debug::evaluating 5 versions
[pull_requests/test_pr]   💬  ::debug::matched: 3.7.6
[pull_requests/test_pr]   💬  ::debug::checking cache: /opt/hostedtoolcache/Python/3.7.6/x64
[pull_requests/test_pr]   💬  ::debug::Found tool in cache Python 3.7.6 x64
[pull_requests/test_pr]   ⚙  ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.7.6/x64
[pull_requests/test_pr]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64
[pull_requests/test_pr]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64/bin
[pull_requests/test_pr]   ⚙  ::set-output:: python-version=3.7.6
| Successfully setup CPython (3.7.6)
[pull_requests/test_pr]   ❓   ##[add-matcher]/actions/actions-setup-python@v2/.github/python.json
[pull_requests/test_pr]   ✅   Success - Set up Python

Here are the respective lines from the setup-python action:
github.com/actions/setup-python@807b74f98c/dist/index.js (L999-L1023)

Here is my lsb-release file:

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

$ uname -a
Linux DESKTOP-WINDOWS10 4.19.104-microsoft-standard #1 SMP Wed Feb 19 06:37:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

EDIT: Removed my previous invalid comment

@grische commented on GitHub (Jun 18, 2020): I created a simple test file which re-creates the problem ```yaml name: pull_requests on: [pull_request] jobs: test_pr: runs-on: ubuntu-18.04 steps: - name: Set up Python uses: actions/setup-python@v2 with: python-version: "3.7" ``` It is fixed by adding the `-P` parameter like the following: ``` $ act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04 pull_request [pull_requests/test_pr] 🚀 Start image=nektos/act-environments-ubuntu:18.04 [pull_requests/test_pr] 🐳 docker run image=nektos/act-environments-ubuntu:18.04 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [pull_requests/test_pr] ⭐ Run Set up Python [pull_requests/test_pr] ☁ git clone 'https://github.com/actions/setup-python' # ref=v2 [pull_requests/test_pr] 🐳 docker cp src=/home/user/.cache/act/actions-setup-python@v2 dst=/actions/ [pull_requests/test_pr] 💬 ::debug::Semantic version spec of 3.7 is 3.7 [pull_requests/test_pr] 💬 ::debug::isExplicit: [pull_requests/test_pr] 💬 ::debug::explicit? false [pull_requests/test_pr] 💬 ::debug::isExplicit: 2.7.17 [pull_requests/test_pr] 💬 ::debug::explicit? true [pull_requests/test_pr] 💬 ::debug::isExplicit: 3.5.9 [pull_requests/test_pr] 💬 ::debug::explicit? true [pull_requests/test_pr] 💬 ::debug::isExplicit: 3.6.10 [pull_requests/test_pr] 💬 ::debug::explicit? true [pull_requests/test_pr] 💬 ::debug::isExplicit: 3.7.6 [pull_requests/test_pr] 💬 ::debug::explicit? true [pull_requests/test_pr] 💬 ::debug::isExplicit: 3.8.1 [pull_requests/test_pr] 💬 ::debug::explicit? true [pull_requests/test_pr] 💬 ::debug::evaluating 5 versions [pull_requests/test_pr] 💬 ::debug::matched: 3.7.6 [pull_requests/test_pr] 💬 ::debug::checking cache: /opt/hostedtoolcache/Python/3.7.6/x64 [pull_requests/test_pr] 💬 ::debug::Found tool in cache Python 3.7.6 x64 [pull_requests/test_pr] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.7.6/x64 [pull_requests/test_pr] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64 [pull_requests/test_pr] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.7.6/x64/bin [pull_requests/test_pr] ⚙ ::set-output:: python-version=3.7.6 | Successfully setup CPython (3.7.6) [pull_requests/test_pr] ❓ ##[add-matcher]/actions/actions-setup-python@v2/.github/python.json [pull_requests/test_pr] ✅ Success - Set up Python ``` Here are the respective lines from the setup-python action: https://github.com/actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/dist/index.js#L999-L1023 Here is my lsb-release file: ``` $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" ``` ``` $ uname -a Linux DESKTOP-WINDOWS10 4.19.104-microsoft-standard #1 SMP Wed Feb 19 06:37:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` EDIT: Removed my previous invalid comment

kerem commented

Author

Owner

@b1llow commented on GitHub (Jul 16, 2020):

the problem still exists

@b1llow commented on GitHub (Jul 16, 2020): the problem still exists

kerem commented

Author

Owner

@dskvr commented on GitHub (Jul 16, 2020):

In order for this to work, one would write a docker file using nektos/act-environments-ubuntu:18.04 as a base image (FROM nektos/act-environments-ubuntu:18.04) that would need to include all caveats listed here.

Sounds like @rgarrigue tried something like this without success. Bummer.

@dskvr commented on GitHub (Jul 16, 2020): In order for this to work, one would write a docker file using `nektos/act-environments-ubuntu:18.04` as a base image (`FROM nektos/act-environments-ubuntu:18.04`) that would need to include all caveats listed [here](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner). Sounds like @rgarrigue tried something like this without success. Bummer.

kerem commented

Author

Owner

@raleighlittles commented on GitHub (Sep 7, 2020):

Still having this problem as well, running Ubuntu 20.04.1 LTS, with 5.4.0-42-generic as my kernel (if that helps or matters at all).

@raleighlittles commented on GitHub (Sep 7, 2020): Still having this problem as well, running Ubuntu 20.04.1 LTS, with 5.4.0-42-generic as my kernel (if that helps or matters at all).

kerem commented

Author

Owner

@aeryncaen commented on GitHub (Sep 10, 2020):

Still a frelling issue

@aeryncaen commented on GitHub (Sep 10, 2020): Still a frelling issue

kerem commented

Author

Owner

@maxphillipsdev commented on GitHub (Sep 21, 2020):

I just ran into this issue as well :(

@maxphillipsdev commented on GitHub (Sep 21, 2020): I just ran into this issue as well :( ![Screen Shot 2020-09-21 at 7 33 04 PM](https://user-images.githubusercontent.com/16758612/93751998-4bc9c200-fbfe-11ea-8a04-8ebec787761d.png)

kerem commented

Author

Owner

@rickstaa commented on GitHub (Sep 22, 2020):

I solved this by using the method explained by @grische.

@rickstaa commented on GitHub (Sep 22, 2020): I solved this by using the method explained by @grische.

kerem commented

Author

Owner

@noliran commented on GitHub (Oct 9, 2020):

Found the problem -
@actions/tool-cache:lib/manifest.js uses _readLinuxVersionFile() to determine the version of the ubuntu distribution using the line DISTRIB_RELEASE=18.04 in /etc/lsb-release .
This file doesn't exist in node:12.6-buster-slim, the default image act currently uses.
I'm currently using this as workaround:

      - run: |
          # Hack to get setup-python to work on act
          if [ ! -f "/etc/lsb-release" ] ; then
            echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release
          fi

Not really sure what's the right fix here - It doesn't make sense that @actions/setup-python treats Ubuntu's release version as platform_version and hands out Python versions based on it. That doesn't make sense..

@noliran commented on GitHub (Oct 9, 2020): Found the problem - `@actions/tool-cache`:`lib/manifest.js` uses `_readLinuxVersionFile()` to determine the version of the ubuntu distribution using the line `DISTRIB_RELEASE=18.04` in `/etc/lsb-release` . This file doesn't exist in node:12.6-buster-slim, the default image act currently uses. I'm currently using this as workaround: ```yaml - run: | # Hack to get setup-python to work on act if [ ! -f "/etc/lsb-release" ] ; then echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release fi ``` Not really sure what's the right fix here - It doesn't make sense that @actions/setup-python treats Ubuntu's release version as `platform_version` and hands out Python versions based on it. That doesn't make sense..

kerem commented

Author

Owner

@charlielito commented on GitHub (Oct 18, 2020):

Same problem with Ubuntu20.04, @noliran solution solved it

@charlielito commented on GitHub (Oct 18, 2020): Same problem with Ubuntu20.04, @noliran solution solved it

kerem commented

Author

Owner

@rickstaa commented on GitHub (Nov 1, 2020):

@noliran his solution worked for me. I use it in the following way:

# Pull request ci config file
# Note: For local testing with https://github.com/nektos/act use the
# `sudo act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04` command.
name: MLC pull CI

on:
  # Trigger the workflow on a pull request,
  # but only for the master branch
  pull_request:
    branches:
      - master

jobs:
  build:
    name: runner / build
    runs-on: ubuntu-18.04
    steps:
      - uses: actions/checkout@v2
      - name: local-fix
        run: |
          # Hack to get setup-python to work on act
          # (see https://github.com/nektos/act/issues/251)
          if [ ! -f "/etc/lsb-release" ] ; then
            echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release
          fi
      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: "3.8"

@rickstaa commented on GitHub (Nov 1, 2020): @noliran his solution worked for me. I use it in the following way: ```yaml # Pull request ci config file # Note: For local testing with https://github.com/nektos/act use the # `sudo act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04` command. name: MLC pull CI on: # Trigger the workflow on a pull request, # but only for the master branch pull_request: branches: - master jobs: build: name: runner / build runs-on: ubuntu-18.04 steps: - uses: actions/checkout@v2 - name: local-fix run: | # Hack to get setup-python to work on act # (see https://github.com/nektos/act/issues/251) if [ ! -f "/etc/lsb-release" ] ; then echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release fi - name: Set up Python uses: actions/setup-python@v2 with: python-version: "3.8" ```

kerem commented

Author

Owner

@rickstaa commented on GitHub (Nov 1, 2020):

Related to this pull request https://github.com/actions/toolkit/pull/594.

@rickstaa commented on GitHub (Nov 1, 2020): Related to this pull request https://github.com/actions/toolkit/pull/594.

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Jan 16, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Jan 16, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@raleighlittles commented on GitHub (Jan 16, 2021):

The PR fixing this issue still hasn't been merged.

@raleighlittles commented on GitHub (Jan 16, 2021): The PR fixing this issue still hasn't been merged.

kerem commented

Author

Owner

@bashbang commented on GitHub (Feb 16, 2021):

This has still been a problem for me on my OSX. I incorporated the "hack" that @noliran mentioned above and deleted the /Users/{myusername}/.cache/act/* and now works as expected.

      - run: |
          # Hack to get setup-python to work on act
          if [ ! -f "/etc/lsb-release" ] ; then
            echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release
          fi

@bashbang commented on GitHub (Feb 16, 2021): This has still been a problem for me on my OSX. I incorporated the "hack" that @noliran mentioned above and deleted the /Users/{myusername}/.cache/act/* and now works as expected. > ```yaml > - run: | > # Hack to get setup-python to work on act > if [ ! -f "/etc/lsb-release" ] ; then > echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release > fi > ```

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Mar 19, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Mar 19, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@dgw commented on GitHub (Mar 27, 2021):

Still waiting on actions/toolkit#594

@dgw commented on GitHub (Mar 27, 2021): Still waiting on actions/toolkit#594

kerem commented

Author

Owner

@catthehacker commented on GitHub (Mar 29, 2021):

Hi all, if you will use medium or large image (https://github.com/nektos/act#runners) there shouldn't be any problem as those include lsb-release which will successfully provide OS version to setup-python.
As this is external issue, I will close this.

@catthehacker commented on GitHub (Mar 29, 2021): Hi all, if you will use `medium` or `large` image (https://github.com/nektos/act#runners) there shouldn't be any problem as those include `lsb-release` which will successfully provide OS version to `setup-python`. As this is external issue, I will close this.

kerem commented

Author

Owner

@GatlenCulp commented on GitHub (Jul 22, 2024):

It's 2024 and this is still an issue

@GatlenCulp commented on GitHub (Jul 22, 2024): It's 2024 and this is still an issue ![GatlenScreen_001029 2024-07-22_14 42 (Code)@2x](https://github.com/user-attachments/assets/6cb56481-10c8-4a1f-b03e-fa4d8c35dc8b) ![GatlenScreen_001035 2024-07-22_14 44 (Code)@2x](https://github.com/user-attachments/assets/87e22b8b-50e0-432d-8523-161e28b994fd) ![GatlenScreen_001031 2024-07-22_14 42 (Code)@2x](https://github.com/user-attachments/assets/c7dc8662-a8f9-4c4c-ac71-da68773110fb) ![GatlenScreen_001033 2024-07-22_14 43 (Code)@2x](https://github.com/user-attachments/assets/b2e586c0-163c-4e81-9afe-c290cf2772bd)

kerem commented

Author

Owner

@planetf1 commented on GitHub (Jan 28, 2025):

Just hit this same problem - using both medium and large act configuration

@planetf1 commented on GitHub (Jan 28, 2025): Just hit this same problem - using both medium and large act configuration

kerem commented