Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
setup-buildx-action messes up already installed buildx on self-hosted runner.
See original GitHub issueSteps to reproduce this issue
Install self hosted actions runner as directed here https://stackoverflow.com/questions/66137419/how-to-enable-non-docker-actions-to-access-docker-created-files-on-my-self-hoste & enable experimental features to enable buildx
Run a github action that sets up buildx, then uses the login action, and then the buildx action
observe the error
Expected behaviour
It builds correctly Actual behaviour
I get an error
on:
push:
branches:
- '**'
name: UH Schedule CI
defaults:
run:
working-directory: 'uh/schedule'
jobs:
test:
name: Test
runs-on: [self-hosted, linux, x64]
container: node:14-slim
steps:
- uses: actions/checkout@v2
- run: yarn install --frozen-lockfile --non-interactive
- run: yarn build
working-directory: sdk
- run: yarn test
test_with_redis:
services:
redis:
image: redis:6-alpine
ports:
- 6379:6379
name: Test with Redis
runs-on: [self-hosted, linux, x64]
container: node:14-slim
env:
REDIS_URL: redis://redis:6379
steps:
- uses: actions/checkout@v2
- run: yarn install --frozen-lockfile --non-interactive
- run: yarn build
working-directory: sdk
- run: yarn test
lint:
name: Lint
runs-on: [self-hosted, linux, x64]
container: node:14-slim
steps:
- uses: actions/checkout@v2
- run: yarn install --frozen-lockfile --non-interactive
- run: yarn build
working-directory: sdk
- run: yarn lint
build_push_beta:
name: Build and Push beta
runs-on: [self-hosted, linux, x64]
steps:
- uses: actions/checkout@v2
- uses: docker/setup-buildx-action@v1
- uses: docker/login-action@v1
with:
registry: xxx
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
- name: Build and push Docker images
uses: docker/build-push-action@v2
with:
context: .
tags: xxx/xx:${{ github.sha }}
push: true
build-args: |
workspace=uh/schedule
build_push_prod:
name: Build and Push prod
needs:
- test
- test_with_redis
- lint
runs-on: [self-hosted, linux, x64]
if: startsWith(github.ref, 'refs/tags/') && endsWith(github.ref, 'v*' )
steps:
- uses: actions/checkout@v2
- uses: actions/github-script@v3
with:
id: tag
script: |
return context.payload.ref.replace(/\/refs\/tags\//, '');
result-encoding: string
- uses: docker/setup-buildx-action@v1
- uses: docker/login-action@v1
with:
registry: xxx
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
- name: Build and push Docker images
uses: docker/build-push-action@v2
with:
tags: xxx/xx:${{ steps.tag.outputs.result }}
push: true
build-args: |
workspace=uh/schedule
Removing the docker setup-buildx-action makes everything work as expected.
Related issue: https://github.com/docker/build-push-action/issues/292
Is there a way to make the setup buildx action basically do nothing when buildx is already installed and setup?
Edit: adding driver: docker fixes this
- uses: docker/setup-buildx-action@v1
with:
driver: docker
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (4 by maintainers)
Top Results From Across the Web
How to enable non-docker actions to access ... - Stack Overflow
A better solution is using rootless docker: Remove docker from your system if you have previously installed it through Ubuntu's default ...
Read more >Configuring your builder - Docker Documentation
Configuring your builder. This page contains instructions on configuring your BuildKit instances when using our Setup Buildx Action.
Read more >Developer news about Docker - Changelog
Docker is a platform built for developers to build and run applications. ... Dashy is a self-hosted dashboard for your homelab.
Read more >Troubleshooting Omnibus GitLab installation issues
On SELinux-enabled systems the Git user's .ssh directory or its contents can get their security context messed up. You can fix this by...
Read more >armv7 docker image created with QEMU action causes Illegal ...
I build my docker images on Github, for three architectures at once. ... QEMU uses: docker/setup-qemu-action@v1 - name: Set up Docker Buildx ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok thanks for your feedback, closing this issue as it’s a dup of docker/build-push-action#292 you have opened previously. Will catch up there.
From the same run: