Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes builder is not cleaned when action is cancelled #279

Closed
3 tasks done
gvisca opened this issue Sep 27, 2023 · 1 comment
Closed
3 tasks done

Kubernetes builder is not cleaned when action is cancelled #279

gvisca opened this issue Sep 27, 2023 · 1 comment

Comments

@gvisca
Copy link

gvisca commented Sep 27, 2023

Contributing guidelines

I've found a bug, and:

  • The documentation does not mention anything about my problem
  • There are no open or closed issues that are related to my problem

Description

When using the kubernetes driver, the buildx builder instance is not cleaned up when the job is cancelled.

image

Expected behaviour

The Post Set up Docker Buildx step run even if the job is cancelled.

Actual behaviour

The Post Set up Docker Buildx step is also cancelled leaving dangling builders.

Repository URL

No response

Workflow run URL

No response

YAML workflow

- name: Set up Docker Buildx
        id: setup-builder
        uses: docker/setup-buildx-action@v3
        with:
          driver: kubernetes
          platforms: linux/amd64
          driver-opts: |
            namespace=actions-runner-system,"nodeselector=kubernetes.io/arch=amd64",requests.cpu=2,requests.memory=2Gi
          append: |
            - platforms: linux/arm64
              driver-opts:
                - namespace=actions-runner-system,"nodeselector=kubernetes.io/arch=arm64",requests.cpu=2,requests.memory=2Gi

Workflow logs

No response

BuildKit logs

No response

Additional info

No response

@crazy-max
Copy link
Member

Seems to be a duplicate of #270.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants