> 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/configure-the-snyk-cli/environment-variables-for-snyk-cli.md). # Environment variables for Snyk CLI The environment variables you can use to configure the Snyk CLI This page identifies environment variables that you can use to configure specific settings for the CLI. ## Configure max network attempts `SNYK_MAX_ATTEMPTS` Starting with Snyk CLI v1.1303.2 `SNYK_MAX_ATTEMPTS=` can be used to enable network level retries. The default value is 1, which means that a network request will fail after one failed attempt. Increasing the value will make the network stack retry retriable status codes. The parameter can be used to mitigate transient network failures at the cost of increased runtime. The range is from 1 to 2,147,483,648 times. Alternatively, you can set the value using the command line parameter `--max-attempts=`. ## Configure the CLI Cache folder `SNYK_CACHE_PATH` By specifying the environment variable `SNYK_CACHE_PATH`, you can define the path to the folder where the CLI will cache files. You must meet the [access requirements](/developer-tools/snyk-cli/security-concept-of-operations-for-snyk/access-requirements.md) for the folder specified. ## Configure a timeout for CLI operations `SNYK_TIMEOUT_SECS` When you specify an environment variable such as `SNYK_TIMEOUT_SECS=60`, the CLI will cancel all operations after 60 seconds and exit with exit code 69. The timeout can range from 1 to 2,147,483,648 seconds, approximately 596.523 hours. ## Configure authentication for container registries `SNYK_REGISTRY_USERNAME` For the `snyk container` commands, specify a `USERNAME` to use when connecting to a container registry. Note that using the `--username` option overrides this value. This value is ignored in favor of local Docker binary credentials when Docker is present. `SNYK_REGISTRY_PASSWORD` For the `snyk container` commands, specify a `PASSWORD` to use when connecting to a container registry. Note that using the `--password` option overrides this value. This is ignored in favor of local Docker binary credentials when Docker is present. ## Configure CLI settings You can set the following environment variable to change CLI settings. `SNYK_CFG_` By specifying this variable, you can override any key that is also available as a `snyk config` option. For example, `SNYK_CFG_ORG=myorg` overrides the default `ORG` in `config` with `myorg`. --- # 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/configure-the-snyk-cli/environment-variables-for-snyk-cli.md?ask=&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.