-
Notifications
You must be signed in to change notification settings - Fork 56
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
Unable to build images on arm64 #101
Comments
Hi there @palmsey I'm running into a similar issue, so I was wondering if you ever got this to work and kept a working config somewhere ? Thanks in advance! |
Sorry, I didn't find a solution for this and eventually switched to GH Actions. |
thanks for the prompt reply @palmsey ! For What It's Worth (FWIW), I did eventually manage to get this going. |
Curious if you can elaborate on how you fixed this issue, @gsaslis -- I am getting past initial mount issues by using a concourse arm64 image as you suggested, but when I attempt to use the oci_build_task image to build an image it fails with a similar "runc run failed: unable to start container process: can't copy bootstrap data to pipe: write init-p: broken pipe". At the moment my hypothesis is that I also need an arm64 oci_build_task. It's not clear if "I did eventually manage to get this going" you mean "concourse runs on an m1" OR "concourse runs on an M1 and can build images with the oci-build-task image" -- the latter is what I'm trying to do. |
I have a task definition like
When I run it on my M1 Mac, when it gets to the first
RUN
command in the Dockerfile I get the error:When I run it in a linux/amd64 EC2 instance, the same task completes successfully. I'm using the docker-compose from the QuickStart, but with the concourse image changed to
rdclda/concourse:7.8.2
sinceconcourse/concourse
won't run on my M1.The full file is:
The text was updated successfully, but these errors were encountered: