Closed bartekpacia closed 4 months ago
Could you please run file $(which cirrus)
to verify cirrus
binary is arm64
and not running under Rosetta.
$ file $(which cirrus)
/opt/homebrew/bin/cirrus: Mach-O 64-bit executable arm64
How does your .cirrus.yml
look like (or maybe you can get some reproducible/minimized example)?
P.S. you probably want to use arm_container
instead of just container
if your container engine does not support amd64
architecture, see Linux Containers.
This is my .cirrus.star
:
It references .common.star
, I believe it's not important in this context but just for the sake of it, here it is:
@edigaryev Using arm_container
works for Linux container, but for macOS VM, I encounter #746
Do I understand correctly that the only issue remaining is that this .cirrus.yml
:
macos_instance:
image: ghcr.io/cirruslabs/macos-runner:sonoma
task:
script: uname -a
Causes your cirrus run
to pull the ghcr.io/cirruslabs/macos-runner:sonoma
image?
What does your tart list --source oci | grep macos-runner
look like on the machine you're trying to run this?
Do I understand correctly that the only issue remaining is [...]
No, the issue is that when I try to run the image, it throws the error from OP.
What does your
tart list --source oci | grep macos-runner
look like on the machine you're trying to run this?
$ tart list --source oci | grep macos-runner
OCI ghcr.io/cirruslabs/macos-runner:sonoma 250 142 stopped
OCI ghcr.io/cirruslabs/macos-runner@sha256:e1847298815e8363d590ac31bf08951f9b00f329954cf7a273bd29317085753b 250 142 stopped
Weirdly, everything seems to work just fine now. I think the most productive thing to do is to close this issue. If I encounter the problem again, I'll create a fully reproducible example.
Thanks for all the help.
My environment
In my project, I'm in the process of migrating to
ghcr.io/cirruslabs/macos-runner:sonoma
. However, when I run the workflow, I always get:This was not occuring before. FWIW, a similar problem also occurs with Linux containers