-
Notifications
You must be signed in to change notification settings - Fork 16
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
Support M1 (arm64) Macs #67
Comments
current show stopper is seems that quay does not provide option for the builders to be of another architecture, so the build of -arm64 flavor fails. May be we are doomed to automate builds on github actions instead of relying on quay, as @vsoch did in http://github.com/singularityhub/singularity-docker//blob/HEAD/.github/workflows/build-containers.yaml |
@yarikoptic we don't build in quay, we just push there. |
oh right you noted that, and this is a totally different issue! lol wonk wonk someone needs to put on her glasses... squintysarus |
so we need to
-arm64
wheneveruname -m
says arm64.NB I was wondering if we could move provisioning of image we do in https://github.com/ReproNim/containers/blob/master/scripts/Dockerfile.singularity-shim to somehow to be done at initial run-time -- then we could avoid needing to build our image at all. But it would also make it less trivial to update and harder to troubleshoot. so let's stay with built images but may be move over to quay.io for them
The text was updated successfully, but these errors were encountered: