[GH-ISSUE #458] Warn that not Apple Silicon compatible #322

Closed
opened 2026-03-01 21:42:22 +03:00 by kerem · 5 comments
Owner

Originally created by @bencooper222 on GitHub (Jan 3, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/458

I'm guessing you're blocked by Docker in terms of Apple Silicon compatibility. Would you be amenable to a PR warning of that on the README?

Originally created by @bencooper222 on GitHub (Jan 3, 2021). Original GitHub issue: https://github.com/nektos/act/issues/458 I'm guessing you're blocked by Docker in terms of Apple Silicon compatibility. Would you be amenable to a PR warning of that on the README?
kerem closed this issue 2026-03-01 21:42:22 +03:00
Author
Owner

@catthehacker commented on GitHub (Jan 3, 2021):

As far as I know, Docker Desktop for Mac already supports Apple Silicon CPUs.

And today we have released to our preview users two exciting features that we know a lot of people have been waiting for: Docker Desktop on Apple M1 chips, and GPU support on WSL 2.

<!-- gh-comment-id:753663520 --> @catthehacker commented on GitHub (Jan 3, 2021): [As far as I know, Docker Desktop for Mac already supports Apple Silicon CPUs.](https://www.docker.com/blog/docker-desktop-3-0-0-smaller-faster-releases/) > And today we have released to our preview users two exciting features that we know a lot of people have been waiting for: Docker Desktop on Apple M1 chips, and GPU support on WSL 2.
Author
Owner

@bencooper222 commented on GitHub (Jan 3, 2021):

Not reasonable to expect this repo to support a preview feature IMO but good to hear it's coming soon!

<!-- gh-comment-id:753669984 --> @bencooper222 commented on GitHub (Jan 3, 2021): Not reasonable to expect this repo to support a preview feature IMO but good to hear it's coming soon!
Author
Owner

@tylerrasor commented on GitHub (Jan 26, 2021):

I've been using the dev preview of docker for about a month now (Preview5 and now Preview7), and it's pretty good.

I downloaded the x86 v0.2.19 release, and the binary runs fine under Rosetta 2. I also pulled master and make install builds fine also using go 1.16beta1 (although Big Sur put restrictions on /usr/local/bin so you have to sudo).

The interesting news: @catthehacker is already pushing arm64 images for ubuntu:act-latest, which the docker preview (correctly) pulls down. I don't know enough about GitHub Actions to know what kind of workers they're running on, but I'd be surprised if they're arm. So my local testing has diverged (if ever so slightly) from what a real actions run would do.

For example, in testing a job that requires actions/setup-go@v2, their action successfully identifies that I'm running an ubuntu arm64 image and then pulls down go*linux-arm64.tar.gz. If I tried an action that wasn't architecture aware, though, I could see it causing problems.

For the time being, I've done a manual docker pull catthehacker/ubuntu:act-latest --platform amd64, which equally works fine.

<!-- gh-comment-id:767259919 --> @tylerrasor commented on GitHub (Jan 26, 2021): I've been using the dev preview of docker for about a month now (`Preview5` and now `Preview7`), and it's pretty good. I downloaded the `x86 v0.2.19` release, and the binary runs fine under Rosetta 2. I also pulled `master` and `make install` builds fine also using `go 1.16beta1` (although Big Sur put restrictions on `/usr/local/bin` so you have to `sudo`). The interesting news: @catthehacker is already pushing `arm64` images for `ubuntu:act-latest`, which the docker preview (correctly) pulls down. I don't know enough about GitHub Actions to know what kind of workers they're running on, but I'd be surprised if they're arm. So my local testing has diverged (if ever so slightly) from what a real actions run would do. For example, in testing a job that requires `actions/setup-go@v2`, their action successfully identifies that I'm running an `ubuntu arm64` image and then pulls down `go*linux-arm64.tar.gz`. If I tried an action that wasn't architecture aware, though, I could see it causing problems. For the time being, I've done a manual `docker pull catthehacker/ubuntu:act-latest --platform amd64`, which equally works fine.
Author
Owner

@catthehacker commented on GitHub (Jan 26, 2021):

@tylerrasor thank you 😸 I'm trying to have the image work on every platform possible (unfortunately, it depends on the platforms provided by ubuntu image on DockerHub) as well as work with every action (while still maintaining small size).

GitHub Actions runners are running 64-bit versions of Ubuntu and any other platform is supported via qemu/Docker.

Free to to bother me whenever something doesn't work on those images (https://github.com/catthehacker/docker_images).

<!-- gh-comment-id:767364585 --> @catthehacker commented on GitHub (Jan 26, 2021): @tylerrasor thank you 😸 I'm trying to have the image work on every platform possible (unfortunately, it depends on the platforms provided by `ubuntu` image on DockerHub) as well as work with every action (while still maintaining small size). GitHub Actions runners are running 64-bit versions of Ubuntu and any other platform is supported via qemu/Docker. Free to to bother me whenever something doesn't work on those images (https://github.com/catthehacker/docker_images).
Author
Owner

@percy-raskova commented on GitHub (Jun 29, 2025):

🔒 Security Classification Needed

This issue appears to mention security-related topics but doesn't have a security classification label.

Please add one of the following labels:

  • security:public - For non-sensitive security discussions
  • security:candidate - For member-only security content
  • security:cadre - For highly sensitive security matters

If this issue doesn't actually contain security-sensitive information, you can ignore this message.

<!-- gh-comment-id:3016354500 --> @percy-raskova commented on GitHub (Jun 29, 2025): 🔒 **Security Classification Needed** This issue appears to mention security-related topics but doesn't have a security classification label. Please add one of the following labels: - `security:public` - For non-sensitive security discussions - `security:candidate` - For member-only security content - `security:cadre` - For highly sensitive security matters If this issue doesn't actually contain security-sensitive information, you can ignore this message.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#322
No description provided.