Python 3.8 removed from latest ubuntu runners

[mjclarke94]

Python 3.8 is not present on the latest runner images for ubuntu, as it is no longer actively maintained. Not only does this result in a need to pin to older runner images, but means the deployment workflow relies on a version of python which doesn't receive security updates anymore.

Unpinning to just use whatever python version is present on the runner image might be the cleanest solution here.

[benpankow]

Thanks for the report, Matt - I believe to address this we'll need to publish a new dagster-cloud.pex on a more recent Python version - right now we only have published one for 3.8.

[ezpzbz]

@benpankow is there any tentative timeline when this is gonna happen? We still need to use ubuntu-20.04.
I just tried with action v0.1.43 and failed with the same reason
/usr/bin/env: ‘python3.8’: No such file or directory

[joscha]

This started appearing about 2h ago with Ubuntu 22.04 runners for me:

In the Validate configuration step:

Run dagster-io/dagster-cloud-action/actions/utils/dagster-cloud-cli@v0.1
  with:
    command: ci check --project-dir . --dagster-cloud-yaml-path dagster_cloud.yaml
  env:
    DAGSTER_CLOUD_API_TOKEN: ***
    ENABLE_FAST_DEPLOYS: true
    PYTHON_VERSION: 3.1.2
    DAGSTER_CLOUD_YAML_PATH: .
    DAGSTER_CLOUD_FILE: dagster_cloud.yaml
    DAGSTER_CLOUD_ORGANIZATION: my-org
    GITHUB_TOKEN: ***
Run $GITHUB_ACTION_PATH/../../../generated/gha/dagster-cloud.pex -m dagster_cloud_cli.entrypoint ci check --project-dir . --dagster-cloud-yaml-path dagster_cloud.yaml
  $GITHUB_ACTION_PATH/../../../generated/gha/dagster-cloud.pex -m dagster_cloud_cli.entrypoint ci check --project-dir . --dagster-cloud-yaml-path dagster_cloud.yaml
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    DAGSTER_CLOUD_API_TOKEN: ***
    ENABLE_FAST_DEPLOYS: true
    PYTHON_VERSION: 3.12
    DAGSTER_CLOUD_YAML_PATH: .
    DAGSTER_CLOUD_FILE: dagster_cloud.yaml
    DAGSTER_CLOUD_ORGANIZATION: my-org
    GITHUB_TOKEN: ***
/usr/bin/env: ‘python3.8’: No such file or directory

[joscha]

Fixing to e6088ea makes it pass:

Run dagster-io/dagster-cloud-action/actions/utils/dagster-cloud-cli@e6088ea2927d484263ee49a9c76ebc847fb30ec5
Run $GITHUB_ACTION_PATH/../../../generated/gha/dagster-cloud.pex -m dagster_cloud_cli.entrypoint ci check --project-dir . --dagster-cloud-yaml-path dagster_cloud.yaml
  
✅[dagster_cloud.yaml] Checked OK
✅[dagster.cloud connection] Able to connect to dagster.cloud
  | Connecting to https://my-org.dagster.cloud/ using DAGSTER_CLOUD_API_TOKEN
  | Connection successful
Passed: 2

[gibsondan]

@joscha can you give a full action yaml that reproduces the problem that you’re seeing? The commit you linked was pushed to main but not to any tags or releases, so it would be surprising for it to cause any new problems here.

[gibsondan]

There’s a new GitHub action release for every Dagster release now - if you change “v0.1” to “v1.10.20” are you still experiencing issues?

[joscha]

I am using a copy of this one: https://github.com/dagster-io/dagster-cloud-serverless-quickstart/blob/main/.github/workflows/dagster-plus-deploy.yml - the only difference is 3.12 for python.

[joscha]

This diff:

diff --git a/.github/workflows/dagster-plus-deploy.yml b/.github/workflows/dagster-plus-deploy.yml
index 0a363b3..b2df89e 100644
--- a/.github/workflows/dagster-plus-deploy.yml
+++ b/.github/workflows/dagster-plus-deploy.yml
@@ -34,7 +34,7 @@ jobs:
       - name: Validate configuration
         id: ci-validate
         if: steps.prerun.outputs.result != 'skip'
-        uses: dagster-io/dagster-cloud-action/actions/utils/dagster-cloud-cli@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/utils/dagster-cloud-cli@982f5b3941e93f9f90e7b44edabcfc5e0325dc60
         with:
           command: "ci check --project-dir ${{ env.DAGSTER_CLOUD_YAML_PATH }} --dagster-cloud-yaml-path ${{ env.DAGSTER_CLOUD_FILE }}"
       - name: Configure dependency resolution to use a prebuilt wheel

fixes the validate step. 982f5b3 is the commit 2 before this change

[gibsondan]

Does it work better if you use v1.10.20? V0.1 is not the same as the latest commit.

…

On Mon, Jun 23, 2025 at 7:50 PM Joscha Feth ***@***.***> wrote: *joscha* left a comment (dagster-io/dagster-cloud-action#163) <#163 (comment)> This diff: diff --git a/.github/workflows/dagster-plus-deploy.yml b/.github/workflows/dagster-plus-deploy.yml index 0a363b3..b2df89e 100644--- a/.github/workflows/dagster-plus-deploy.yml+++ b/.github/workflows/dagster-plus-deploy.yml@@ -34,7 +34,7 @@ jobs: - name: Validate configuration id: ci-validate if: steps.prerun.outputs.result != 'skip'- uses: ***@***.***+ uses: ***@***.*** with: command: "ci check --project-dir ${{ env.DAGSTER_CLOUD_YAML_PATH }} --dagster-cloud-yaml-path ${{ env.DAGSTER_CLOUD_FILE }}" - name: Configure dependency resolution to use a prebuilt wheel fixes the validate step. 982f5b3 <982f5b3> is the commit 2 before this change — Reply to this email directly, view it on GitHub <#163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAPJC4OSBDRIXVGDDLHL6T3FCHDVAVCNFSM6AAAAAB76WAM4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOJYGMYDSNRXGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[joscha]

There’s a new GitHub action release for every Dagster release now - if you change “v0.1” to “v1.10.20” are you still experiencing issues?

v1.10.20 works for me, but whatever is behind v0.1 does not anymore since ~2h ago. No code changes on my behalf. I even reran a previously passing build and it is reliably failing now.

[gibsondan]

Got it, thanks for reporting that. I believe we know what was going on there, and v0.1 should be working again as expected again now.

…

On Mon, Jun 23, 2025 at 7:53 PM Joscha Feth ***@***.***> wrote: *joscha* left a comment (dagster-io/dagster-cloud-action#163) <#163 (comment)> There’s a new GitHub action release for every Dagster release now - if you change “v0.1” to “v1.10.20” are you still experiencing issues? v1.10.20 works for me, but whatever is behind v0.1 does not anymore since ~2h ago. No code changes on my behalf. I even reran a previously passing build and it is reliably failing now. — Reply to this email directly, view it on GitHub <#163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAPJCZXSIO7ZW3KPGWA37L3FCHRLAVCNFSM6AAAAAB76WAM4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOJYGMYTKMRXHE> . You are receiving this because you commented.Message ID: ***@***.***>

[joscha]

Actually, looking more closely, I can see the diff:

Passing build:

Download action repository 'dagster-io/dagster-cloud-action@v0.1' (SHA:d171ed1a18af759478b2613279bf6bdf2a6587e4)

Failing build:

Download action repository 'dagster-io/dagster-cloud-action@v0.1' (SHA:468e62b8d19354adb44c5c1495cdaf27212a3191)

so it's the diff between d171ed1a18af759478b2613279bf6bdf2a6587e4 and 468e62b8d19354adb44c5c1495cdaf27212a3191 (commits)

It doesn't make immediate sense, also not why it would appear now, but the 0.1 version definitely resolves to two different shas in each of the builds and the runner image is the same for both:

Runner Image
  Image: ubuntu-22.04
  Version: 20250602.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20250602.1/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20250602.1