APT and RPM repositories at repositories.timber.io will be decommissioned on February 28th Migration instructions

Install Vector

Get up and running with Vector on your preferred platform

Vector compiles to a single static binary, which makes it easy to install.

On *nix systems Vector’s only dependency is libc. Your operating system should generally provide this dependency.

Using static musl builds

We also release Vector artifacts that are statically linked with musl for the libc implementation, which results in a static binary with no dependencies (these have musl in their name). These dependency-free artifacts can be useful in stripped-down environments that don’t provide a built-in libc implementation.

musl performance issues
Please note that musl, as of this writing, has a significantly worse performance profile than glibc when Vector is running in multiple threads (Vector defaults to the number of available cores). We recommend that you use glibc when available unless you’re running Vector on a single CPU.

Installation script

This light-weight script detects your platform and determine the best method for installing Vector:

curl --proto '=https' --tlsv1.2 -sSfL https://sh.vector.dev | bash
curl --proto '=https' --tlsv1.2 -sSfL https://sh.vector.dev | bash -s -- -y

You can use the --prefix option to specify a custom installation directory. This is especially useful in automated environments (for example Dockerfiles).

The following command adds the required binaries to $PATH without modifying your profiles.

RUN apk add --no-cache curl bash && \ 
    curl --proto '=https' --tlsv1.2 -sSfL https://sh.vector.dev | bash -s -- -y --prefix /usr/local

Other installation methods

If you prefer a more granular method for installing Vector, check out these subsections of the documentation for alternatives: