-
Notifications
You must be signed in to change notification settings - Fork 109
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
Document Arm Containers #905
Conversation
Is there an issue where arm doesn't upload the logs? See for example: https://cirrus-ci.com/task/4712248254922752?logs=clone#L1 |
@MarcoFalke sorry for the inconvenience. We were testing and changing some last things. Now everything should work as expected |
There seem to be some more issues: https://cirrus-ci.com/task/5504774142427136 (Or is this a bug in our config?) |
Maybe an intermittent issue? In our repo it still works fine. Edit: Or maybe it can't run from a Dockerfile? |
@MarcoFalke, yeah, |
Oh okay, I see, thank for letting us know! |
Similar to platform guessing we can check if the instances has "Arm" in the type url. Related to cirruslabs/cirrus-ci-docs#905 (comment)
@real-or-random actually now it's much simpler since GCP has Arm instances added #1027. Adding some parser improvements in cirruslabs/cirrus-cli#586 and shortly after we should be able to add |
Sounds great!
Yep, and I also believe that's in general the better of the two alternatives. |
* Advanced archiotecture guessing Similar to platform guessing we can check if the instances has "Arm" in the type url. Related to cirruslabs/cirrus-ci-docs#905 (comment) * Use scaleway worker
TLDR now you can use
arm_container
instead ofcontainer
to runarm64
containers.Fixes #218