You will need roughly 2 minutes to read this article.
In order to run the
jet binary on your computer, you need to have Docker installed and configured, with a running Docker host such as Docker For Mac.
Please follow the steps below for the operating system you are using. See the Jet Release Notes for the ChangeLog.
See the sha256sums file for checksums for the latest release. To check the downloaded files on Linux / Unix based systems run the following command.
shasum -c -a 256 sha256sums
brew cask install codeship/taps/jet
If you don’t have Homebrew installed or don’t use Homebrew Cask you can install
jet via the following commands.
curl -SLO "https://s3.amazonaws.com/codeship-jet-releases/2.6.1/jet-darwin_amd64_2.6.1.tar.gz" tar -xC /usr/local/bin/ -f jet-darwin_amd64_2.6.1.tar.gz chmod u+x /usr/local/bin/jet
curl -SLO "https://s3.amazonaws.com/codeship-jet-releases/2.6.1/jet-linux_amd64_2.6.1.tar.gz" sudo tar -xaC /usr/local/bin -f jet-linux_amd64_2.6.1.tar.gz sudo chmod +x /usr/local/bin/jet
There is no supported Jet version for Windows machines, although Windows Subsystem For Linux works for many of our customers.
The above version is statically linked and will work the same way on all platforms. But it doesn’t support certain features, e.g. resolving
.local DNS names. If your builds require this, please use the dynamically linked version instead.
Once this is done you can check that Jet is working by running
jet help. This will print output similar to the following.
$ jet version 2.6.1 $ jet help Usage: jet [command] ...
jet is installed, you can use the
jet update command to quickly update to the newest version. You can read the jet update documentation for more information.
DOCKER_HOST must be set.
DOCKER_CERT_PATH are respected in the same way as with the official Docker client. If you installed Docker via Docker For Mac this is typically done by default during installation.
If you installed and configured your Docker environment via Docker Machine (and you are on OS X or Linux) and named the environment dev, running the following command will set those variables.
eval $(docker-machine env dev)
Do you think we need to improve this article? If so, please submit our feedback form to help us improve this article!