> 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/prerequisites-for-cli-and-jenkins-plugin-on-alpine-linux-operating-system.md).

# Prerequisites for CLI and Jenkins plugin on Alpine Linux operating system

Prerequisites for the Snyk CLI and Jenkins plugin on Alpine Linux

Before running Snyk CLI and Snyk Jenkins plugin on the Alpine Linux operating system, follow these steps to establish the prerequisites:

1. Ensure that `libstdc++` is installed.\
   To install `libstdc++`, open a terminal from within the relevant container and run `apk add libstdc++` .\
   The command either adds the shared library to your container environment or returns `OK` if the shared library is already installed in `/usr/lib`.
2. Ensure that Snyk CLI version 1.185.5 or above is installed on your system.\
   Snyk recommends that you install the **latest** version.
3. To use the Snyk Jenkins plugin, ensure also that the Snyk Jenkins plugin v2.10.0 or above is installed.\
   Snyk recommends that you install the **latest** version.
4. After you install the Snyk CLI, you must [authenticate](/developer-tools/snyk-cli/authenticate-to-use-the-cli.md).

For additional information, see [Install or update the Snyk CLI](/developer-tools/snyk-cli/install-the-snyk-cli.md) and [Jenkins Plugin](/developer-tools/integrations/snyk-ci-cd-integrations/jenkins-plugin-integration-with-snyk.md) in the CI/CD docs.


---

# 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/prerequisites-for-cli-and-jenkins-plugin-on-alpine-linux-operating-system.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.