Installing packages¶

Tip

👉 Would you rather watch a short video tutorial? Check it our here: installing packages.

Warning

Do not install packages by running !pip install <package-name> inside your Jupyter Notebook. This causes the package to be installed every time you run the pipeline step. It is not saved in the environment as containers are stateless!

Orchest runs all your individual pipeline steps (e.g. .ipynb or .R scripts) in containers. The default images are based on the Jupyter Docker Stacks and come with a number of pre-installed packages.

To install additional packages or to run other terminal commands inside the base image, we support custom environments. We essentially create a new image by running your script inside the selected base image.

Note

If an environment is in use by an active Jupyter kernel, then changes to the environment require a restart of the kernel (which can be done through the JupyterLab UI).

Build an environment¶

Simply go to Environments in the left menu pane.
Create a new Environment. Environments are part of a single project.
Choose an Environment name.
Choose a base image. This image will be extended through your setup bash script. Custom images must have USER root or sudo must be installed, find must also be installed.
To keep environment image sizes to a minimal, each environment is tied to a specific programming language. Choose one of the supported languages for your environment.
Go to the BUILD tab to install additional packages by adding their installation steps to the Environment set-up script, e.g. pip install tensorflow or sudo apt-get install gcc.
Finally, press the Build button at the bottom.

Tip

The shell script that installs the additional packages is run inside the /project-dir, meaning that you can directly interact with your project files from within the script. For example:

#!/bin/bash

# Install any dependencies you have in this shell script.

# E.g. pip install tensorflow
pip install -r requirements.txt