circleci-public / arm-preview-docs Goto Github PK

Hi, I took a look at the ARM preview today.

Unfortunately, the existing ARM executor sizes are too small for us. Our Golang-based backend is fairly large, and we use use 2xlarge executors.

Will there be larger executors available further into the preview?

We use a locally built image for our Circle workflows, since there are a large number of dependencies that we don't want to spend time installing at build time.

Is it (or will it) be possible to use custom aarch64 images on ARM executors?

Thanks!

I get /bin/bash: line 1: ./BrowserStackLocal: cannot execute binary file: Exec format error when i execute a command from Browserstack local app. this is not an issue on a Linux VM.

Just found out while testing Android SDK on an emulator with CircleCi that has ARM architecture, doesn't support emulator tests.

Using the arm with the following

  deploy:
    machine:
      image: ubuntu-2204:2022.07.1
    resource_class: arm.medium
    steps:
        - run:
            command: jq

returns the following:

-bash: /usr/local/bin/jq: cannot execute binary file: Exec format error

Seems the preinstalled jq is not for ARM

Removing /usr/local/bin/jq and reinstalling with sudo apt-get install jq solves the issues as it installs the arm build (i am assuming). Does mean that jq commands need to be rewritten as /usr/bin/jq ... however.

The only thing I can think about regarding naming in this system is that Arm is the company, but they design chips with several different instruction sets, and it's a meaningful difference. "arm64" (or less commonly "aarch64") is the 64-bit ARMv8 instruction set found in modern server processors, and the text should reflect any understanding that it's primarily 64-bit support (or if you do provide 32-bit support like for "armhf" or "armel" found on Raspberry Pi's) that's clear.

cc @appplemac @WorksOnArm

Hello 👋

I was looking into trying out the arm machine executor to properly compile binaries for macos machines.
Binaries are compiled using Vercel's pkg CLI.

One of the requirements for signing the binaries for macos is by using codesign:

codesign --sign - <executable>

This is done automatically by pkg but it assumes that the codesign executable is available in the machine.

Is that something that can be provided in the arm machine?

Thanks 🤗

We started using the ARM instances in our orb and parameterized the executor on our jobs to enable matrix builds for both intel and ARM. All looking good so far: https://github.com/elementary-robotics/atom/blob/latest/.circleci/atom.yml#L194

We had previously been cross-compiling ARM using the buildx QEMU simulation and were able to drop-in the new executors with no apparent issues so far. Thanks!