Install JFrog CLI

This procedure installs JFrog CLI V2 on your system. JFrog CLI is a command-line tool that provides a unified interface for interacting with JFrog Platform services, including Artifactory, Xray, and Distribution. Installing JFrog CLI enables you to automate artifact management, security scanning, and CI/CD workflows from the command line.

This topic covers the following tasks:

Install JFrog CLI — download the executable
JFrog CLI V2 "jf" Installers — install using the jf executable name (recommended)
JFrog CLI V2 "jfrog" Installers — install using the jfrog executable name
JFrog CLI v1 (Legacy) Installers — legacy installation (deprecated)
Verify Installation — confirm the CLI is working
Shell Completion — enable tab-based auto-complete
Troubleshooting — resolve common installation issues

Prerequisites

Before installing JFrog CLI, ensure you have:

A supported operating system: macOS (Intel or Apple Silicon), Linux (x86_64, ARM64), or Windows (x86_64)
Internet access to download the binary (or a pre-downloaded binary for air-gapped environments)
Shell access (bash, zsh, or fish on macOS/Linux. PowerShell or cmd on Windows)

Supported Platforms

OS	Architecture	Install Methods
macOS	Intel (x86_64), Apple Silicon (ARM64)	Homebrew, cURL, npm, Docker
Linux	x86_64, ARM64	Homebrew, Debian, RPM, cURL, npm, Docker
Windows	x86_64	Chocolatey, PowerShell, npm, Docker
Docker	Any (via container)	`docker pull`

JFrog CLI V2 was launched in July 2021. It includes changes to the functionality and usage of some of the legacy JFrog CLI commands. The changes are the result of user feedback submitted through GitHub, making the usage and functionality easier and more intuitive. For example, some of the default values changed and are now more consistent across different commands. This version includes improved and restructured code, as well as replacing old and deprecated functionality.

Most of the changes included in V2 are breaking changes compared to the V1 releases. JFrog CLI V2 packages these changes to allow migration when you are ready.

New enhancements to JFrog CLI are planned to be introduced as part of V2 only. V1 receives very little development attention nowadays. If you haven't yet migrated to V2, you are encouraged to do so.

Install JFrog CLI

To download the executable, visit the JFrog CLI Download Site.

You can also download the sources from the JFrog CLI Project on GitHub. There you will also find instructions on how to build JFrog CLI.

The legacy name of JFrog CLI's executable is jfrog. New installers are now available to make CLI usage easier and more convenient. A series of new installers install JFrog CLI with the new jf executable name. For backward compatibility, the old installers remain available. The best practice is to migrate to the newer jf executable name.

📘
Note
: Homebrew installation provides both jf and jfrog executables pointing to the same binary. You can use either command interchangeably.

Choosing an Install Method

Use the table below to pick the right method for your situation:

Scenario	Recommended method
macOS or Linux daily use	Homebrew — easiest to install and update
CI/CD pipeline or automated environment	Install with cUrl (system-wide) — single command, no package manager required
Air-gapped or restricted environment	Download Locally with cUrl — download binary once, move to any machine
JavaScript/Node.js project	npm — but only if you are not using nvm or Volta (see note below)
Running CLI without installing	Docker — no local installation required
Windows machine	Chocolatey or PowerShell

🚧
Warning — avoid mixing install methods on the same machine
: Installing JFrog CLI via more than one method (for example, both Homebrew and npm) can result in different versions on the same system. Whichever appears first in PATH wins. For example, an npm-installed version in an nvm-managed bin/ directory typically takes precedence over a Homebrew installation. After installing, run which jf to confirm you are using the intended binary, and jf --version to confirm the expected version.

JFrog CLI V2 "jf" Installers

The following installers are available for JFrog CLI V2. These installers make JFrog CLI available through the jf executable.

Homebrew (macOS/Linux)

Homebrew is the recommended installation method for macOS and Linux desktop users. It provides automatic updates and manages dependencies.

To install JFrog CLI using Homebrew:

Run the following command:
```
brew install jfrog-cli
```
Verify the installation:
```
jf --version
```
Run the intro command to see initial setup instructions:
```
jf intro
```

📘
Note
: If you have already configured a JFrog server, jf intro produces no output. This is expected behavior.

Debian

Use the Debian package manager to install JFrog CLI on Debian-based Linux distributions.

To install JFrog CLI on Debian:

Create the keyrings directory, download the GPG key, add the repository, and install JFrog CLI:

sudo mkdir -p /usr/share/keyrings
curl -fsSL https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-debs/keyPairs/primary/public | sudo gpg --dearmor -o /usr/share/keyrings/jfrog.gpg 
echo "deb [signed-by=/usr/share/keyrings/jfrog.gpg] https://releases.jfrog.io/artifactory/jfrog-debs focal contrib" | sudo tee /etc/apt/sources.list.d/jfrog.list 
sudo apt update
sudo apt install -y jfrog-cli-v2-jf

Verify the installation:
```
jf --version
```
Run the intro command to see initial setup instructions:
```
jf intro
```

📘
Note
: If you have already configured a JFrog server, jf intro produces no output. This is expected behavior.

RPM (RHEL/CentOS/Fedora)

Use the YUM package manager to install JFrog CLI on RHEL, CentOS, or Fedora distributions.

To install JFrog CLI using RPM:

Create the repository file, import GPG keys, and install JFrog CLI:

echo "[jfrog-cli]" > jfrog-cli.repo
echo "name=JFrog CLI" >> jfrog-cli.repo
echo "baseurl=https://releases.jfrog.io/artifactory/jfrog-rpms" >> jfrog-cli.repo
echo "enabled=1" >> jfrog-cli.repo
echo "gpgcheck=1" >> jfrog-cli.repo
rpm --import https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-rpms/keyPairs/primary/public
rpm --import https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-rpms/keyPairs/secondary/public
sudo mv jfrog-cli.repo /etc/yum.repos.d/
sudo yum install -y jfrog-cli-v2-jf

Verify the installation:
```
jf --version
```
Run the intro command to see initial setup instructions:
```
jf intro
```

📘
Note
: If you have already configured a JFrog server, jf intro produces no output. This is expected behavior.

Install System-Wide with cUrl (Recommended for CI/CD)

This method downloads and installs JFrog CLI to a system directory. Requires sudo access. This is the recommended method for CI/CD pipelines and automated environments.

To install JFrog CLI system-wide using cUrl:

Run the following command:

curl -fL https://install-cli.jfrog.io | sh

📘
Note
: This script attempts to install to /usr/local/bin or /usr/bin. You will be prompted for your password if sudo is required.

Download Locally with cUrl (No sudo required)

Downloads the jf executable to the current directory. Use this method when you do not have sudo access, or want to install JFrog CLI for a single user without touching system directories.

To download JFrog CLI locally using cUrl:

Download the binary to the current directory:
```
curl -fL https://getcli.jfrog.io/v2-jf | sh
```
Move the binary to a directory in your PATH:
```
mv jf ~/bin/
```
Verify the installation:
```
./jf --version
```

📘
Note
: The installer sets the executable bit automatically. Running chmod +x jf is not necessary.

NPM

📘
Note
Avoid npm-based installation if you are using shim-based version managers (like nvm or Volta). These tools place their own bin/ directory at the front of PATH, which means an npm-installed jf will silently shadow any version installed via Homebrew or cURL. If you have both an npm-installed and a Homebrew-installed JFrog CLI, which jf will resolve to the npm version regardless of what Homebrew reports. Use a non-npm install method unless your project specifically requires npm.

To install JFrog CLI using npm:

Run the following command:
```
npm install -g jfrog-cli-v2-jf
```
Verify the installation:
```
jf --version
```

Docker

Use Docker to run JFrog CLI without a local installation. This is useful for ephemeral environments or when you do not want to install the CLI on the host machine.

📘
Prerequisite
: Docker Desktop or the Docker daemon must be running before executing these commands.

macOS: Open Docker Desktop from your Applications folder and wait for it to finish starting (the whale icon in the menu bar becomes steady).

Linux: Start the Docker daemon with sudo systemctl start docker.

Windows: Open Docker Desktop from the Start menu.

To run JFrog CLI using Docker:

Run one of the following Docker images:

Slim Image (minimal, ~80MB):

docker run releases-docker.jfrog.io/jfrog/jfrog-cli-v2-jf jf -v

Full Image (includes additional tools):

docker run releases-docker.jfrog.io/jfrog/jfrog-cli-full-v2-jf jf -v

Interactive Usage:

docker run -it -v ~/.jfrog:/root/.jfrog releases-docker.jfrog.io/jfrog/jfrog-cli-v2-jf jf --help

Cleanup Docker Images:

docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli-v2-jf
docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli-full-v2-jf

PowerShell (Windows)

To install JFrog CLI using PowerShell:

Run the following command in an elevated PowerShell session:

Start-Process -Wait -Verb RunAs powershell '-NoProfile iwr https://releases.jfrog.io/artifactory/jfrog-cli/v2-jf/[RELEASE]/jfrog-cli-windows-amd64/jf.exe -OutFile $env:SYSTEMROOT\system32\jf.exe'

📘
Note
: Replace [RELEASE] with a specific version number (for example, 2.88.0) or keep as [RELEASE] for the latest version.

Chocolatey (Windows)

To install JFrog CLI using Chocolatey:

Run the following command:
```
choco install jfrog-cli-v2-jf
```

JFrog CLI V2 "jfrog" Installers

The following installers are available for JFrog CLI V2. These installers make JFrog CLI available through the jfrog executable.

Homebrew (macOS/Linux)

📘
Note
: This is the same formula as the "jf" installer. Both jf and jfrog commands are installed and work identically.

To install JFrog CLI using Homebrew (jfrog executable):

Run the following command:
```
brew install jfrog-cli
```
Verify the installation:
```
jfrog --version
```

Debian

To install JFrog CLI on Debian (jfrog executable):

Create the keyrings directory, download the GPG key, add the repository, and install JFrog CLI:

sudo mkdir -p /usr/share/keyrings
curl -fsSL https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-debs/keyPairs/primary/public | sudo gpg --dearmor -o /usr/share/keyrings/jfrog.gpg
echo "deb [signed-by=/usr/share/keyrings/jfrog.gpg] https://releases.jfrog.io/artifactory/jfrog-debs xenial contrib" | sudo tee /etc/apt/sources.list.d/jfrog.list
sudo apt update
sudo apt install -y jfrog-cli-v2

Verify the installation:
```
jfrog --version
```

RPM (RHEL/CentOS/Fedora)

To install JFrog CLI using RPM (jfrog executable):

Create the repository file, import the GPG key, and install JFrog CLI:

echo "[jfrog-cli]" > jfrog-cli.repo
echo "name=jfrog-cli" >> jfrog-cli.repo
echo "baseurl=https://releases.jfrog.io/artifactory/jfrog-rpms" >> jfrog-cli.repo
echo "enabled=1" >> jfrog-cli.repo
echo "gpgcheck=1" >> jfrog-cli.repo
rpm --import https://releases.jfrog.io/artifactory/jfrog-gpg-public/jfrog_public_gpg.key
sudo mv jfrog-cli.repo /etc/yum.repos.d/
sudo yum install -y jfrog-cli-v2

Verify the installation:
```
jfrog --version
```

Download with cUrl

To download JFrog CLI using cUrl (jfrog executable):

Download the binary:

curl -fL https://getcli.jfrog.io/v2 | sh

Verify the downloaded binary:
```
./jfrog --version
```

NPM

📘
Note
Avoid npm-based installation if you are using shim-based version managers (like nvm or Volta). These tools place their own bin/ directory at the front of PATH, which means an npm-installed jfrog will silently shadow any version installed via Homebrew or cURL. Use a non-npm install method unless your project specifically requires npm.

To install JFrog CLI using npm (jfrog executable):

Run the following command:
```
npm install -g jfrog-cli-v2
```
Verify the installation:
```
jfrog --version
```

Docker

📘
Prerequisite
: Docker Desktop or the Docker daemon must be running before executing these commands.

macOS: Open Docker Desktop from your Applications folder and wait for it to finish starting.

Linux: Start the Docker daemon with sudo systemctl start docker.

Windows: Open Docker Desktop from the Start menu.

To run JFrog CLI using Docker (jfrog executable):

Run one of the following Docker images:

Slim Image:

docker run releases-docker.jfrog.io/jfrog/jfrog-cli-v2 jfrog -v

Full Image:

docker run releases-docker.jfrog.io/jfrog/jfrog-cli-full-v2 jfrog -v

Cleanup Docker Images:

docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli-v2
docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli-full-v2

Chocolatey (Windows)

To install JFrog CLI using Chocolatey (jfrog executable):

Run the following command:
```
choco install jfrog-cli
```

List of Changes in JFrog CLI V2

The default value of the --flat option is now set to false for the jfrog rt upload command.
The deprecated syntax of the jfrog rt mvn command is no longer supported. To use the new syntax, the project needs to be first configured using the jfrog rt mvnc command.
The deprecated syntax of the jfrog rt gradle command is no longer supported. To use the new syntax, the project needs to be first configured using the jfrog rt gradlec command.
The deprecated syntax of the jfrog rt npm and jfrog rt npm-ci commands is no longer supported. To use the new syntax, the project needs to be first configured using the jfrog rt npmc command.
The deprecated syntax of the jfrog rt go command is no longer supported. To use the new syntax, the project needs to be first configured using the jfrog rt go-config command.
The deprecated syntax of the jfrog rt nuget command is no longer supported. To use the new syntax, the project needs to be first configured using the jfrog rt nugetc command.
All Bintray commands are removed.
The jfrog rt config command is removed and replaced by the jfrog config add command.
The jfrog rt use command is removed and replaced with the jfrog config use.
The --props command option and props file spec property for the jfrog rt upload command are removed, and replaced with the --target-props command option and targetProps file spec property respectively.
The following commands are removed:
- jfrog rt release-bundle-create
- jfrog rt release-bundle-delete
- jfrog rt release-bundle-distribute
- jfrog rt release-bundle-sign
- jfrog rt release-bundle-update
and replaced with the following commands respectively:
- jfrog ds release-bundle-create
- jfrog ds release-bundle-delete
- jfrog ds release-bundle-distribute
- jfrog ds release-bundle-sign
- jfrog ds release-bundle-update
The jfrog rt go-publish command now only supports Artifactory version 6.10.0 and above. Also, the command no longer accepts the target repository as an argument. The target repository should be pre-configured using the jfrog rt go-config command.
The jfrog rt go command no longer falls back to the VCS when dependencies are not found in Artifactory.
The --deps, --publish-deps, --no-registry and --self options of the jfrog rt go-publish command are now removed.
The --apiKey option is now removed. The API key should now be passed as the value of the --password option.
The --exclude-patterns option is now removed, and replaced with the --exclusions option. The same is true for the excludePatterns file spec property, which is replaced with the exclusions property.
The JFROG_CLI_JCENTER_REMOTE_SERVER and JFROG_CLI_JCENTER_REMOTE_REPO environment variables are now removed and replaced with the JFROG_CLI_EXTRACTORS_REMOTE environment variable.
The JFROG_CLI_HOME environment variable is now removed and replaced with the JFROG_CLI_HOME_DIR environment variable.
The JFROG_CLI_OFFER_CONFIG environment variable is now removed and replaced with the CI environment variable. Setting CI to true disables all prompts.
The directory structure is now changed when the jfrog rt download command is used with placeholders and --flat=false (--flat=false is now the default). When placeholders are used, the value of the --flat option is ignored.
When the jfrog rt upload command now uploads symlinks to Artifactory, the target file referenced by the symlink is uploaded to Artifactory with the symlink name. If the --symlink option is used, the symlink itself (not the referenced file) is uploaded, with the referenced file as a property attached to the file.

JFrog CLI v1 (Legacy) Installers

🚧
Warning
: JFrog CLI v1 is deprecated and receives minimal maintenance. Migrate to JFrog CLI v2 for continued support.

The following installations are available for JFrog CLI v1. These installers make JFrog CLI available through the jfrog executable.

Debian

To install JFrog CLI v1 on Debian:

Create the keyrings directory, download the GPG key, add the repository, and install JFrog CLI:

sudo mkdir -p /usr/share/keyrings
curl -fsSL https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-debs/keyPairs/primary/public | sudo gpg --dearmor -o /usr/share/keyrings/jfrog.gpg
echo "deb [signed-by=/usr/share/keyrings/jfrog.gpg] https://releases.jfrog.io/artifactory/jfrog-debs xenial contrib" | sudo tee /etc/apt/sources.list.d/jfrog.list
sudo apt update
sudo apt install -y jfrog-cli

Verify the installation:
```
jfrog --version
```

RPM (RHEL/CentOS/Fedora)

To install JFrog CLI v1 using RPM:

Create the repository file, import GPG keys, and install JFrog CLI:

echo "[jfrog-cli]" > jfrog-cli.repo
echo "name=jfrog-cli" >> jfrog-cli.repo
echo "baseurl=https://releases.jfrog.io/artifactory/jfrog-rpms" >> jfrog-cli.repo
echo "enabled=1" >> jfrog-cli.repo
echo "gpgcheck=1" >> jfrog-cli.repo
rpm --import https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-rpms/keyPairs/primary/public
rpm --import https://releases.jfrog.io/artifactory/api/v2/repositories/jfrog-rpms/keyPairs/secondary/public
sudo mv jfrog-cli.repo /etc/yum.repos.d/
sudo yum install -y jfrog-cli

Verify the installation:
```
jfrog --version
```

Download with cUrl

To download JFrog CLI v1 using cUrl:

Download the binary:
```
curl -fL https://getcli.jfrog.io | sh
```
Verify the downloaded binary:
```
./jfrog --version
```

NPM

📘
Note
If you are using any shim-based version managers (like Volta or nvm) for a package, avoid using npm-based installation. Use other installation options JFrog provides instead.

To install JFrog CLI v1 using npm:

Run the following command:
```
npm install -g jfrog-cli-go
```
Verify the installation:
```
jfrog --version
```

Docker

📘
Prerequisite
: Docker Desktop or the Docker daemon must be running before executing these commands.

macOS: Open Docker Desktop from your Applications folder and wait for it to finish starting.

Linux: Start the Docker daemon with sudo systemctl start docker.

Windows: Open Docker Desktop from the Start menu.

To run JFrog CLI v1 using Docker:

Run one of the following Docker images:

Slim Image:

docker run releases-docker.jfrog.io/jfrog/jfrog-cli jfrog -v

Full Image:

docker run releases-docker.jfrog.io/jfrog/jfrog-cli-full jfrog -v

Cleanup Docker Images:

docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli
docker rmi releases-docker.jfrog.io/jfrog/jfrog-cli-full

Go

📘
Note
: This installation method is deprecated. Use other installation methods instead.

To install JFrog CLI v1 using Go:

Run the following command:

GO111MODULE=on go install github.com/jfrog/jfrog-cli@latest

Verify the installation (the binary installs to $GOPATH/bin or $HOME/go/bin):
```
jfrog-cli --version
```

Optionally rename the binary to jfrog:

mv $(go env GOPATH)/bin/jfrog-cli $(go env GOPATH)/bin/jfrog

Verify Installation

After installation, verify JFrog CLI is working correctly.

To verify JFrog CLI is installed correctly:

Check the version:
```
jf -v
```
Expected output:
```
jf version 2.x.x
```
Note: You may see [Error] messages about a plugin (for example, failed getting signature from plugin: 'rt-fs') printed before the version string. These are unrelated to the installation and do not indicate a failure — they mean a previously installed plugin has a permission issue. See Troubleshooting below.

View available commands:

jf --help

Expected output (truncated):

NAME:
   jf - See https://docs.jfrog.com/integrations/docs/jfrog-cli for full documentation.

USAGE:
   jf [global options] command [command options] [arguments...]

COMMANDS:
   config, c     Server configurations commands.
   rt            Artifactory commands.
   xr            Xray commands.
   ...

Check available environment variables:

jf options

Expected output (truncated):

    JFROG_CLI_LOG_LEVEL
        [Default: INFO]
        This variable determines the log level of the JFrog CLI.

    JFROG_CLI_HOME_DIR
        [Default: ~/.jfrog]
        Defines the JFrog CLI home directory path.
    ...

View current server configuration (if any):
```
jf config show
```
Expected output (if a server has been configured):
```
Server ID:          my-server
JFrog Platform URL: https://mycompany.jfrog.io/
Artifactory URL:    https://mycompany.jfrog.io/artifactory/
User:               myuser
Default:            true
```
If no server has been configured yet, this command produces no output. Configure a server with jf config add. See Authenticating via the CLI for details.
Confirm the correct binary is on your PATH:
```
which jf
```
The cURL system-wide installer places the binary in /usr/local/bin/jf. If you have multiple install methods active (for example, Homebrew and npm), this command shows which one takes precedence. If the wrong version is reported by jf -v, check the output of which jf and adjust your PATH accordingly.

If you see command not found, the CLI binary is not in your system PATH. Add the directory containing jf to your PATH:

Linux/macOS:
```
export PATH=$PATH:/usr/local/bin
```
Windows (PowerShell):
```
Get-Command jf
$env:PATH += ";C:\path\to\jfrog-cli"
```

Shell Completion

After installation, enable shell completion for tab-based auto-complete. The --install command generates the completion script file. You must then activate it in your current shell session and optionally make it permanent by adding the activation lines to your shell profile.

Bash

To enable shell completion for Bash:

Generate the completion script:
```
jf completion bash --install
```

Activate for the current session and make permanent:

source ~/.jfrog/jfrog_bash_completion
echo 'source ~/.jfrog/jfrog_bash_completion' >> ~/.bashrc

Zsh

To enable shell completion for Zsh:

Generate the completion script:
```
jf completion zsh --install
```

Activate for the current session:

autoload -Uz compinit
compinit
source ~/.jfrog/jfrog_zsh_completion

Make permanent by adding these three lines to ~/.zshrc:

autoload -Uz compinit
compinit
source ~/.jfrog/jfrog_zsh_completion

Fish

To enable shell completion for Fish:

Generate the completion script:
```
jf completion fish --install
```
Activate for the current session:
```
source ~/.jfrog/jfrog_fish_completion
```
Make permanent by adding the following to ~/.config/fish/config.fish:
```
source ~/.jfrog/jfrog_fish_completion
```

Troubleshooting

`command not found: jf`

The jf binary is not in your PATH. Run which jf to check whether it is installed at all. If the binary exists but is in a non-standard directory, add that directory to PATH:

export PATH=$PATH:/usr/local/bin   # adjust path as needed

To make this permanent, add the export line to your shell profile (~/.zshrc, ~/.bashrc, or similar).

Plugin error: `failed getting signature from plugin` on every command

You may see messages like the following printed before the output of any jf command:

[Error] jfrog cli plugins: failed getting signature from plugin: 'my-plugin'. Skiping...
[Error] Error was: fork/exec ~/.jfrog/plugins/my-plugin/bin/my-plugin: permission denied

This means a plugin binary in ~/.jfrog/plugins/ is not executable. Fix it with:

chmod +x ~/.jfrog/plugins/<plugin-name>/bin/<plugin-name>

Replace <plugin-name> with the name shown in the error. If you no longer need the plugin, remove it:

jf plugin uninstall <plugin-name>

This error does not affect normal CLI operation — all built-in commands still work correctly.

Wrong version reported after Homebrew install

If brew install jfrog-cli reports one version but jf --version reports an older one, another installation of JFrog CLI (typically via npm or nvm) is shadowing the Homebrew binary in your PATH. Run:

which jf

If the path points to an nvm or npm directory (for example, ~/.nvm/versions/node/.../bin/jf), either uninstall the npm version or reorder your PATH so /usr/local/bin (Homebrew) appears before the nvm path.

Docker command fails: `failed to connect to the docker API`

The full error looks like:

failed to connect to the docker API at unix:///.../.docker/run/docker.sock; check if the path is correct and if the daemon is running

The Docker daemon is not running. Start it before running any docker run commands:

macOS: Open Docker Desktop from your Applications folder. Wait until the whale icon in the menu bar stops animating.
Linux: Run sudo systemctl start docker.
Windows: Open Docker Desktop from the Start menu.

`jf intro` produces no output

This is expected when a JFrog server has already been configured. The intro message is only shown on first use. To view your configured servers, run:

jf config show

Prerequisites

Supported Platforms

Install JFrog CLI

Choosing an Install Method

JFrog CLI V2 "jf" Installers

Homebrew (macOS/Linux)

Debian

RPM (RHEL/CentOS/Fedora)

Install System-Wide with cUrl (Recommended for CI/CD)

Download Locally with cUrl (No sudo required)

NPM

Docker

PowerShell (Windows)

Chocolatey (Windows)

JFrog CLI V2 "jfrog" Installers

Homebrew (macOS/Linux)

Debian

RPM (RHEL/CentOS/Fedora)

Download with cUrl

NPM

Docker

Chocolatey (Windows)

List of Changes in JFrog CLI V2

JFrog CLI v1 (Legacy) Installers

Debian

RPM (RHEL/CentOS/Fedora)

Download with cUrl

NPM

Docker

Go

Verify Installation

Shell Completion

Bash

Zsh

Fish

Troubleshooting

command not found: jf

Plugin error: failed getting signature from plugin on every command

Wrong version reported after Homebrew install

Docker command fails: failed to connect to the docker API

jf intro produces no output

`command not found: jf`

Plugin error: `failed getting signature from plugin` on every command

Docker command fails: `failed to connect to the docker API`

`jf intro` produces no output