---
title: Custom environments
description: Describes how to build a custom environment when a custom model requires something not contained in one of DataRobot's built-in environments.

---

# Custom environments {: #custom-environments }

Once uploaded into DataRobot, custom models run inside of environments&mdash;Docker containers running in Kubernetes. In other words, DataRobot copies the uploaded files defining the custom task into the image container. In most cases, adding a custom environment is not required because there are a variety of built-in environments available in DataRobot. Python and/or R packages can be easily added to these environments by uploading a `requirements.txt` file with the task’s code. A custom environment is only required when a custom task:

* Requires additional Linux packages.
* Requires a different operating system.
* Uses a language other than Python, R, or Java.

This document describes how to build a custom environment for these cases. To assemble and test a custom environment locally, install both Docker Desktop and the [DataRobot user model (DRUM) CLI tool](custom-model-drum) on your machine.

## Custom environment guidelines {: #custom-environment-guidelines }

!!! note 
    DataRobot recommends using an environment template and not building your own environment except for specific use cases. (For example, you don't want to use DRUM but you want to implement your own prediction server.)

If you'd like to use a tool, language, or framework that is not supported by our template environments, you can make your own. DataRobot recommends modifying the provided environments to suit your needs; however, to make an easy-to-use, re-usable environment, you should adhere to the following guidelines:

* Your environment must include a Dockerfile that installs any requirements you may want.

* Custom models require a simple webserver to make predictions. DataRobot recommends putting this in your environment so you can reuse it with multiple models. The webserver must be listening on port `8080` and implement the following routes:

    !!! note 
        `URL_PREFIX` is an environment variable that is available at runtime. It must be added to the routes below.

    Mandatory endpoints | Description
    --------------------|------------
    `GET /URL_PREFIX/`  | This route is used to check if your model's server is running.
    `POST /URL_PREFIX/predict/` | This route is used to make predictions.

    Optional extension endpoints | Description
    -----------------------------|------------
    `GET /URL_PREFIX/stats/` | This route is used to fetch memory usage data for DataRobot Custom Model Testing.
    `GET /URL_PREFIX/health/` | This route is used to check if model is loaded and functioning properly. If model loading fails error with 513 response code should be returned. Failing to handle this case may cause the backend k8s container to enter crash and enter a restart loop for several minutes.

* An executable `start_server.sh` file is required to start the model server.

* Any code and `start_server.sh` should be copied to `/opt/code/` by your Dockerfile.

!!! note
    To learn more about the complete API specification, you can review the [DRUM server API `yaml` file](https://github.com/datarobot/datarobot-user-models/blob/master/custom_model_runner/drum_server_api.yaml){ target=_blank }.

## Create the environment {: #create-the-environment }

Once DRUM is installed, begin your environment creation by copying one of the examples from [GitHub](https://github.com/datarobot/datarobot-user-models/tree/master/public_dropin_environments){ target=_blank }. {% include 'includes/github-sign-in.md' %} Make sure:

1. The environment code stays in a single folder.
2. You remove the `env_info.json` file.

### Add Linux packages {: #add-linux-packages }

To add Linux packages to an environment, add code at the beginning of `dockerfile`, immediately after the `FROM datarobot…` line.

Use `dockerfile` syntax for an Ubuntu base. For example, the following command tells DataRobot which base to use and then to install packages `foo`, `boo`, and `moo` inside the Docker image:

```
FROM datarobot/python3-dropin-env-base
RUN apt-get update --fix-missing && apt-get install foo boo moo
```

### Add Python/R packages {: #add-python-r-packages }

In some cases, you might want to include Python/R packages in the environment. To do so, note the following:

* List packages to install in `requirements.txt`. For R packages, do not include versions in the list.

* Do not mix Python and R packages in the same `requirements.txt` file. Instead, create multiple files and adjust `dockerfile` so DataRobot can find and use them.

## Test the environment locally {: #test-the-environment-locally }

The following example illustrates how to quickly test your environment using Docker tools and DRUM.

1. To test a custom task with a custom environment, navigate to the local folder where the task content is stored.

2. Run the following, replacing placeholder names in `< >` brackets with actual names:

	``` sh
	drum fit --code-dir <path_to_task_content> --docker <path_to_a_folder_with_environment_code> --input <path_to_test_data.csv> --target-type <target_type> --target <target_column_name> --verbose
	```

##  Add a custom environment to DataRobot {: #add-a-custom-environment-to-datarobot }

To add a custom environment, you must upload a compressed folder in `.tar`, `.tar.gz`, or `.zip` format. Be sure to review the guidelines for [preparing a custom environment folder](#custom-environment-guidelines) before proceeding. You may also consider creating a custom [drop-in environment](drop-in-environments) by adding Scoring Code and a `start_server.sh` file to your environment folder.

Note the following environment limits and environment version limits:

=== "SaaS"
     
     Next to the **Add new environment** and the **New version** buttons, there is a badge indicating how many environments (or environment versions) you've added and how many environments (or environment versions) you can add in total. With the correct permissions, an administrator can set these limits at a [user](manage-users#manage-execution-environment-limits) or [group](manage-groups#manage-execution-environment-limits) level. The following status categories are available in this badge:

=== "Self-Managed"
     
     Next to the **Add new environment** and the **New version** buttons, there is a badge indicating how many environments (or environment versions) you've added and how many environments (or environment versions) you can add in total. With the correct permissions, an administrator can set these limits at a [user](manage-users#manage-execution-environment-limits), [group](manage-groups#manage-execution-environment-limits), or [organization](manage-orgs#manage-execution-environment-limits) level. The following status categories are available in this badge:

Badge | Description
------|------------
![](images/env-limit-badge.png){: style="height:30px; width:auto;"}       | The number of environments is less than 75% of the environment limit.
![](images/env-limit-badge-alert.png){: style="height:30px; width:auto;"} | The number of environments is equal to or greater than 75% of the environment limit.
![](images/env-limit-badge-warn.png){: style="height:30px; width:auto;"}  | The number of environments is equal to the environment limit. You can't add more environments without removing an environment first.


Navigate to **Model Registry** > **Custom Model Workshop** and select the **Environments** tab. This tab lists the environments provided by DataRobot and those you have created. Click **Add new environment** to configure the environment details and add it to the workshop.

![](images/c-env-1.png)

Complete the fields in the **Add New Environment** dialog box.

![](images/c-env-2.png)

| Field | Description    |
| :------------- | :------------- |
| Environment name | The name of the environment. |
| Choose the file you want to upload | The tarball archive containing the Dockerfile and any other relevant files. |
| Programming Language | The language in which the environment was made. |
| Description (optional) | An optional description of the custom environment. |

When all fields are complete, click **Add**. The custom environment is ready for use in the Workshop.

After you upload an environment, it is only available to you unless you [share](#share-and-download-an-environment) it with other individuals.

To make changes to an existing environment, create a new [version](#add-an-environment-version).

### Add an environment version {: #add-an-environment-version }

Troubleshoot or update a custom environment by adding a new version of it to the Workshop. In the **Versions** tab, select **New version**.

![](images/c-env-4.png)

Upload the file for a new version and provide a brief description, then click **Add**.

![](images/c-env-5.png)

The new version is available in the **Verison** tab; all past environment versions are saved for later use.

### View environment information {: #view-environment-information }

There is a variety of information available for each custom and built-in environment. To view:

1. Navigate to **Model Registry > Custom Model Workshop > Environments**. The resulting list shows all environments available to your account, with summary information.

2. For more information on an individual environment, click to select:

	![](images/cml-env-3.png)

	The versions tab lists a variety of version-specific information and provides a link for downloading that version's environment context file.

3. Click **Current Deployments** to see a list of all deployments in which the current environment has been used.

4. Click **Environment Info** to view information about the general environment, not including version information.

### Share and download an environment {: #share-and-download-an-environment }

You can share custom environments with anyone in your organization from the menu options on the right. These options are not available to built-in environments because all organization members have access and these environment options should not be removed.

!!! note
    An environment is not available in the model registry to other users unless it was explicitly shared. That does not, however, limit users' ability to use blueprints that include tasks that use that environment. See the description of [_implicit sharing_](cml-custom-tasks#implicit-sharing) for more information.

From **Model Registry > Custom Model Workshop > Environments**, use the menu to [share and/or delete](custom-model-actions) any custom environment that you have appropriate permissions for. (Note that the link points to custom model actions, but the options are the same for custom tasks and environments.)

![](images/cml-env-4.png)

## Self-Managed AI Platform admins {: #self-managed-ai-platform-admins }

The following is available only on the Self-Managed AI Platform.

###  Environment availability {: #environment-availability }

Each custom environment is either public or private (the default availability). Making an environment public allows other users that are part of the same DataRobot installation to use it without the owner explicitly sharing it or users needing to create and upload their own version. Private environments can only be seen by the owner and the users that the environment has been shared with. Contact your DataRobot system administrator to make a custom environment public.