domino logo
Get started with Python
Step 0: Orient yourself to DominoStep 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get started with R
Step 0: Orient yourself to Domino (R Tutorial)Step 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Domino Reference
Projects
Projects OverviewProjects PortfolioUpload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCompare File RevisionsArchive a Project
Advanced Project Settings
Project DependenciesProject TagsRename a ProjectSet up your Project to Ignore FilesUpload files larger than 550MBExporting Files as a Python or R PackageTransfer Project Ownership
Domino Runs
JobsDiagnostic Statistics with dominostats.jsonNotificationsResultsRun Comparison
Advanced Options for Domino Runs
Run StatesDomino Environment VariablesEnvironment Variables for Secure Credential StorageAccessing the shell for a Domino Run with SSHUse Apache Airflow with Domino
Scheduled Jobs
Domino Workspaces
WorkspacesUse Visual Studio Code in Domino WorkspacesPersist RStudio PreferencesAccess Multiple Hosted Applications in one Workspace Session
Customize the Domino Software Environment
Environment ManagementDomino Standard EnvironmentsInstall Packages and DependenciesAdd Workspace IDEs
Advanced Options for Domino Software Environment
Install Custom Packages in Domino with Git IntegrationAdd Custom DNS Servers to Your Domino EnvironmentConfigure a Compute Environment to User Private Cran/Conda/PyPi MirrorsScala notebooksUse TensorBoard in Jupyter WorkspacesUse MATLAB as a WorkspaceCreate a SAS Data Science Workspace Environment
Publish your Work
Publish a Model API
Model Publishing OverviewModel Invocation SettingsModel Access and CollaborationModel Deployment ConfigurationPromote Projects to Production
Publish a Web Application
App Publishing OverviewGet Started with DashGet Started with ShinyGet Started with Flask
Advanced Web Application Settings in Domino
App Scaling and PerformanceHost HTML Pages from DominoHow to Get the Domino Username of an App Viewer
Launchers
Launchers OverviewAdvanced Launcher Editor
Assets Portfolio Overview
Connect to your Data
Domino Datasets
Datasets OverviewDatasets Best PracticesAbout domino.yamlDatasets Advanced Mode TutorialDatasets Scratch SpacesConvert Legacy Data Sets to Domino Datasets
Data Sources OverviewConnect to Data Sources
Git and Domino
Git Repositories in DominoWork From a Commit ID in Git
Work with Data Best Practices
Work with Big Data in DominoWork with Lots of FilesMove Data Over a Network
Hadoop and Spark
Connect to a Cloudera CDH5 cluster from DominoConnect to a Hortonworks cluster from DominoConnect to a MapR cluster from DominoConnect to an Amazon EMR cluster from DominoHadoop and Spark overviewKerberos authenticationRun local Spark on a Domino executorUse PySpark in Jupyter Workspaces
Advanced User Configuration Settings
Two-factor authenticationUser API KeysOrganizations Overview
Use the Domino Command Line Interface (CLI)
Install the Domino Command Line (CLI)Domino CLI ReferenceDownload Files with the CLIForce-Restore a Local ProjectMove a Project Between Domino DeploymentsUse the Domino CLI Behind a Proxy
Browser Support
Get Help with Domino
Additional ResourcesGet Domino VersionContact Domino Technical Support
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Domino Reference
>
Customize the Domino Software Environment
>
Install Packages and Dependencies

Install Packages and Dependencies

Domino is pre-installed with many common libraries, so we recommend that you first try running your code before customizing your configuration. If you need to, there are specific ways to add your own dependencies for…​

  • Python

  • R

If you have more specialized dependencies, please let us know.

Persistent installations

By default, Domino runs each of your scripts (or interactive sessions) from a fresh environment. This means any packages you install will be installed to your environment each time you start an execution. We have more advanced functionality for managing your own compute environments with software changes that stay permanently installed, which can speed up execution start times. See our section about working with raw Dockerfiles to learn more about creating your own custom environments.

Python

Check what’s already installed

Many common modules are installed by default. To get a list of pre-installed modules, you can include help('modules') at the start of your script or in a new IPython Notebook session. Or using the Domino CLI tool, you can run domino run --direct "pip freeze"

Add your own packages

To specify your own additional dependencies, you can use pip with Domino. To specify module dependencies for your project, add a pip requirements file named requirements.txt to the root of your project folder.

The requirements file specifies which libraries and any version requirements for them. For example:

pandas
lxml==3.2.3
numpy>=1.7.1

For a full reference on the syntax of the requirements file, read this.

If you’re using pip on your local machine, the easiest way to generate the requirements.txt file is to run the following command in the root of your project folder:

~/domino/myProject $ pip freeze > requirements.txt

For performance reasons, you should prune that file so that it includes only the libraries you need for your actual analysis.

Alternatively, if you’re working in a Jupyter Notebook, you can also use pip to install dependencies interactively. In a notebook cell, you can run:

! pip install --user <package>

(The '!' tells the notebook to execute the cell as a shell command.)

Install Packages Hosted from a Git Repository

Caution

Pip can install Python packages from source by cloning a public Git repository over https. For full reference, see here. To specify this, you will need to add something like the following line to your requirements.txt file:

-e git+https://git.yourproject.org/you/Project.git#egg=YourProject

The most common host of Git projects is GitHub. If the package you wish to install is publicly accessible, then the instructions above will work. However, if you need to install any private repositories, Domino can securely integrate with GitHub to access those private repositories. Read our instructions on securely storing your Github credentials.

Caution

R

If you’re using Domino for R scripts, you may also want to check out our R Package for controlling Domino in your R IDE.

Most common packages are installed by default (you can include installed.packages() at the start of your script to print out a list of installed packages). If you need additional packages, you can use R’s built-in package manager to install and load them: simply add install.packages calls for any packages your code needs to the top of your R scripts, for example,

install.packages("rpart", dependencies=TRUE, repos='http://cran.us.r-project.org')
# install other packages...

library('rpart')

# rest of your script...

These package installation calls must be at the top of every R script that Domino runs. If your packages take a long time to install, we recommend that you create a custom compute environment for efficiency.

Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.