Skip to content

Latest commit

 

History

History
145 lines (113 loc) · 6.06 KB

agent_omnibus.md

File metadata and controls

145 lines (113 loc) · 6.06 KB

Build the Agent packages

Agent packages for all the supported platforms are built using Omnibus, which can be run via invoke tasks.

Omnibus creates a package for your operating system, so you'll get a DEB package on Debian-based distros, an RPM package on distros that use RPM, an MSI installer on Windows, or a .pkg package bundled in a DMG archive on Mac.

For Linux, we provide Docker images (one to build DEB packages and one for RPM), with the build dependencies installed, so you don't have to install them on your system.

Building inside Docker (Linux only, recommended)

Use the provided Docker images to build a DEB or RPM package for Linux. You need to have Docker already running on your machine.

From the datadog-agent source folder, use the following command to run the agent.omnibus-build task in a Docker container:

docker run -v "$PWD:/go/src/github.com/DataDog/datadog-agent" -v "/tmp/omnibus:/omnibus" -v "/tmp/opt/datadog-agent:/opt/datadog-agent" -v"/tmp/gems:/gems" --workdir=/go/src/github.com/DataDog/datadog-agent datadog/agent-buildimages-deb_x64 inv -e agent.omnibus-build --base-dir=/omnibus --gem-path=/gems

The container will share 3 volumes with the host to avoid starting from scratch at each Omnibus run:

  • /tmp/omnibus, containing the Omnibus base dir
  • /tmp/opt/datadog-agent, containing the Omnibus installation dir
  • /tmp/gems, containing all the ruby gems installed with Bundler

Note that you can change deb_x64 for rpm_x64 to get an RPM package instead.

If you want to find the Dockerfiles for these images, they are available in the datadog-agent-buildimages git repo. To build them from scratch, you can do so like this:

docker build -t datadog-agent-buildimages:deb_x64 -f deb-x64/Dockerfile .

If the build images crash when you run them on modern Linux distributions, you might be affected by this bug.

Building on your system (Linux and Mac)

The project will be built locally then compressed in the final deb/rpm/dmg artifact. Most of the files will be copied or created under the same installation path of the final package, /opt/datadog-agent, but if you run Omnibus from Linux, some files will be copied into /etc. This means two things:

  • If you already have a Datadog Agent installed, you might need to move it to a different location before operating Omnibus.
  • You need root privileges to build the packages (Linux only).

For these reasons, if you're running Linux we strongly suggest to use a dedicated virtual machine or a Docker container where Omnibus can safely move things around the filesystem without disrupting anything.

To run Omnibus and build the package, make the /opt folder world readable and run:

inv agent.omnibus-build --base-dir=$HOME/.omnibus

On Mac, you might want to skip the signing step by running:

inv agent.omnibus-build --base-dir=$HOME/.omnibus --skip-sign

The path you pass with the --base-dir option will contain the sources downloaded by Omnibus in the src folder, the binaries cached after building those sources in the cache folder and the final deb/rpm/dmg artifacts in the pkg folder. You can fine tune an Omnibus run passing more options, see inv agent.omnibus-build --help for the list of all the available options.

Note: it's strongly advised to pass --base-dir and point to a directory outside the Agent repo. By default Omnibus stores packages in the project folder itself: running the task multiple times would recursively add those artifacts to the source files for the datadog-agent software definition.

Building on Windows

Prerequisites

  • Visual Studio >= 2017
    • Minimal config for VS 2019
       "version": "1.0",
   "components": [
     "Microsoft.VisualStudio.Component.CoreEditor",
     "Microsoft.VisualStudio.Workload.CoreEditor",
     "Microsoft.VisualStudio.Component.NuGet",
     "Microsoft.VisualStudio.Component.Roslyn.Compiler",
     "Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions",
     "Microsoft.Component.MSBuild",
     "Microsoft.VisualStudio.Component.TextTemplating",
     "Microsoft.VisualStudio.Component.IntelliCode",
     "Component.Microsoft.VisualStudio.LiveShare",
     "Microsoft.VisualStudio.Component.VC.CoreIde",
     "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
     "Microsoft.VisualStudio.Component.Graphics.Tools",
     "Microsoft.VisualStudio.Component.VC.DiagnosticTools",
     "Microsoft.VisualStudio.Component.Windows10SDK.18362",
     "Microsoft.VisualStudio.Component.Debugger.JustInTime",
     "Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
     "Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
     "Microsoft.VisualStudio.Component.VC.CMake.Project",
     "Microsoft.VisualStudio.Component.VC.ATL",
     "Microsoft.VisualStudio.Component.VC.TestAdapterForBoostTest",
     "Microsoft.VisualStudio.Component.VC.TestAdapterForGoogleTest",
     "Microsoft.VisualStudio.Component.VC.v141.x86.x64",
     "Microsoft.Component.VC.Runtime.UCRTSDK",
     "Microsoft.VisualStudio.Component.VC.140",
     "Microsoft.VisualStudio.Workload.NativeDesktop"
   ]
 }
  • Windows 8.1 SDK
  • Wix SDK (Also requires the Windows feature '.Net Framework 3.5')
  • 7zip
  • Ruby >= 2.4 and MSYS/MINGW
  • Bundler
  • Python >= 2.7

Note: Windows 8.1 SDK is not longer shipped with Visual Studio, starting with version 2019. It can be downloaded separately.

Installation

  • Launch a "Developer Command Prompt for VS 201X"

  • Enable ridk

      ridk enable

  • Check that the necessary tools are in the %PATH%:

      > which 7z
  /c/Program Files/7-Zip/7z
  > which heat
  /c/Program Files (x86)/WiX Toolset v3.11/bin/heat
  > which bundler
  /c/Ruby24-x64/bin/bundler

  • Launch the build for the packages

      inv agent.omnibus-build --base-dir=C:\.omnibus-ruby