How-to | Install system-level package dependencies#

Sometimes users need access to a library that has prerequisites for system packages that are not natively installed on the underlying operating system. These system packages must be installed before the given Python library can be used. Typically, an administrator with access to the OS installs these system packages.

When Dataiku is deployed to Cloud Stacks (such as on AWS or Azure), you can install system packages through Fleet Manager. To do this:

  1. Launch Fleet Manager.

  2. Under Settings > Instance templates, choose the instance template you want to modify.

  3. Under Setup actions > + New Action, choose Install system packages.

  4. In Packages to install, specify the packages you want to install on the instance, making sure to input only one package name per line.

  5. Save your changes.

Specifying system packages to install on an instance of Dataiku deployed to Cloud Stacks.

You’ll need to replay the setup actions before the changes can take effect.

To replay the setup actions:

  1. From Instances, choose All and locate the running instance.

  2. Right-click the configuration menu (three vertical dots) and choose >_ Replay setup actions.

  3. Select Confirm.

Repeat these steps for each running instance.


Installing system packages on an instance will only install the system packages on the DSS instance(s) defined by the template. More steps are needed to update the images used for containerized execution with the additional system packages. For details about how an administrator with command line access to the DSS server can perform this step, visit Customization of base images, adding system packages.

Alternatively, for DCS deployments, you can run an Ansible task to customize the base images that are built when a node is provisioned. Note that the Ansible task is set to occur at the stage “After DSS install”.


While the system is building the custom base images, you’ll notice an increase in provisioning time.

Running an Ansible task to customize the base image when the node is provisioned.