About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Edit Environment definition

You can change the behavior and/or content of an Environment by editing the Dockerfile instructions.

Order of script execution

Scripts in an Environment are executed in the following order:

  1. Pre Setup scripts

  2. requirements.txt

  3. Post Setup scripts

  4. Pre Run scripts

  5. Post Run scripts (after the Workspace/Job/App has been stopped)

Note

Edit Environment definitions

You can modify an Environment by editing its Dockerfile instructions.

Note

  1. In the navigation pane, click Environments.

  2. Click the name of an Environment.

  3. On the Overview tab, you can modify the description or visibility.

  4. Click Edit Definition to define the Dockerfile and supporting scripts and settings for the Environment. Each time you save changes, the Environment’s revision increments by one and your Domino deployment rebuilds the Environment and pushes it to the local Docker registry.

  5. In Dockerfile Instructions, enter your Dockerfile layers. See Docker’s official site. You can also view the Dockerfile best practices.

  6. In Pluggable Workspace Tools, enter the interactive tools needed by any project that uses this Environment. See Add Workspace IDEs.

  7. In the Run Setup Scripts section, you can enter bash code that is executed at runtime. Domino executes these commands at runtime and runs them as root.

    1. In Pre Run Script, enter commands to execute after the Python packages in your project’s requirements.txt are installed.

    2. In Post Run Script, enter commands to execute after your Workspace/Job/App is stopped.

  8. In the Environment variables section, set the Variable Names and their Values.

  9. Click Advanced if you want to enter bash code that is executed at a specified step in your experiment’s lifecycle.

    1. In Pre Setup Script, enter commands to execute before the Python packages in your project’s requirements.txt are installed.

    2. In Post Setup Script, enter commands to execute after the Python packages in the requirements.txt of your project are installed.

  10. In Revision History, enter a short description about the changes to the Environment.

  11. Click Build.