> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli/using-cli-releases-before-version-1.1230.0-on-an-apple-m1-or-m2-machine.md).

# Using CLI releases before version 1.1230.0 on an Apple M1 or M2 machine

How to run Snyk CLI releases before 1.1230.0 on Apple M1 or M2 machines

**Beginning with version 1.1230.0**, the Snyk CLI supports Apple silicon, including M1 and M2 machines, so **you no longer need the Rosetta 2 software, as suggested on this page**. Snyk recommends always keeping your CLI installation updated to the latest version. You can check which version of the Snyk CLI you have installed by running `snyk --version`.

If you run releases of the Snyk CLI before [version 1.1230.0](https://github.com/snyk/cli/releases/tag/v1.1230.0) on an Apple M1 machine, you may see the following error:

```
$ snyk --version
bad CPU type in executable
```

On an M2 machine, you may see this error:

`Unknown system error -86`

To avoid these errors with releases of Snyk CLI before [version 1.1230.0](https://github.com/snyk/cli/releases/tag/v1.1230.0), install the Apple [Rosetta 2](https://support.apple.com/en-gb/HT211861) software:

`softwareupdate --install-rosetta`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli/using-cli-releases-before-version-1.1230.0-on-an-apple-m1-or-m2-machine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.