Using MATLAB® as a Workspace


Interactive MATLAB® sessions are supported in Domino by means of configuring a Compute Environment and Interactive Workspace. If your administrators have already configured such an environment, you may be able to use it by simply switching your project to that environment.


This page provides the steps necessary to create a suitable Compute Environment if it does not already exist. Some steps may require assistance from a Domino or MATLAB admin.


Network Licensing structure for MATLAB

To get MATLAB working using this guide, you will need a network license. A network concurrent license is recommended, but a network named license may also work IF the usernames specified in the license match the usernames within Domino. If you don’t currently have a network concurrent license, reach out to your MATLAB license administrator to determine if one is available or needs to be purchased. This information will be needed when configuring the Compute Environment (see below). You may have a single license server or a set of 3 license servers. We will show examples for two styles of providing the license server information:

  • The first method requires only the port and host for your license server(s), e.g. (and optionally, This is recommended for most cases.

  • The second method applies if you have been given a network.lic file, e.g.

    SERVER 000000000000 27000
    SERVER 000000000010 27000
    SERVER 000000000020 27000

    This is recommended only if you have multiple sets of license servers (and thus multiple license files), i.e. in the case of separate license servers for MATLAB Parallel Server.

See Mathworks help for more details on the various options or talk to your MATLAB license administrator.

(Optional) Hardware Tiers with the correct GPU drivers

To make full use of GPU capabilities, the hardware tier you are using within Domino needs to have GPU drivers installed that can support the version of MATLAB you want to use. Compatibility is determined by this table describing the minimum CUDA Toolkit version requirement for each version of MATLAB, and by this table describing the minimum NVIDIA driver version requirement for each version of the CUDA Toolkit.

The MATLAB base images provided by Domino (see below) will already have a suitable version of the CUDA Toolkit installed. The NVIDIA drivers must be configured at the Hardware Tier level. If you already have a GPU-enabled hardware tier configured, it is likely that it already has suitable NVIDIA drivers. See the Troubleshooting section below for instructions on how to check the driver version during a MATLAB session to verify it is configured correctly.

If you do not have the correct NVIDIA drivers configured on your GPU Hardware Tier, talk to your Domino administrator and refer them to this sample documentation for configuring NVIDIA drivers in EKS.

Environment Setup

If a MATLAB-specific environment does not already exist in your Domino deployment, you will need to create one. Read about Compute Environment Management if you aren’t already familiar.

Choose a base image

  1. In Domino, click Environments in the top navigation bar.

  2. Click Create Environment.

  3. Give the environment an informative name, and then choose a base image that has MATLAB installed. The following are the most current options available from Domino.


    Repo Link

    MATLAB 2021a

    MATLAB 2020b

    MATLAB 2020a

    MATLAB 2019b

  4. After selecting the appropriate base image, choosing a visibility setting, and optionally providing a description, click Create Environment to finalize.

  5. The environment will be created and you will be automatically redirected to its Overview page. Scroll down to the Docker Settings and click Edit Dockerfile to continue setting up the environment.

Edit the Dockerfile

Add the following lines to your Dockerfile Instructions, editing the license server information to match your actual license servers. Also be sure to edit the MATLAB_VERSION variable to match the MATLAB version of the base image you chose in the previous step.

If you have port and host information for your license servers (recommended method):

# This MATLAB_VERSION variable is used later in persisting Add-ons and preferences
ENV,[email protected],[email protected]

Or, if you have a network.lic file (more useful if you have multiple license files) you can adapt this example:

USER root

# Here we are simply pasting the information in the license file
# If you have the license file hosted somewhere accessible to Domino, you could instead download it to the same location via wget or similar methods
RUN mkdir -p /usr/local/MATLAB/$MATLAB_VERSION/licenses && \
    printf "SERVER 000000000000 27000\nSERVER 000000000010 27000\nSERVER 000000000020 27000\nUSE_SERVER\n" > /usr/local/MATLAB/$MATLAB_VERSION/licenses/network.lic

USER ubuntu

Add Pluggable Workspace Tools definition

Add the appropriate “Pluggable Properties” to the Properties for Workspaces.

These are documented alongside the base image descriptions here:

Note that the MATLAB base images are built on top of the Domino standard environments, so you can add the workspace configs for e.g. Jupyter or RStudio for those standard environments also.

For example, if you are using the base image, add the following lines for the MATLAB workspace:

    title: "MATLAB"
    iconUrl: ""
    start: [ "/var/opt/workspaces/matlab/" ]
        port: 8888
        requireSubdomain: false

Because it is built on top of, you can optionally add any of the following sections for workspaces from that environment:

  title: "Jupyter (Python, R, Julia)"
  iconUrl: "/assets/images/workspace-logos/Jupyter.svg"
  start: [ "/var/opt/workspaces/jupyter/start" ]
    port: 8888
    rewrite: false
    internalPath: "/{{ownerUsername}}/{{projectName}}/{{sessionPathComponent}}/{{runId}}/{{#if pathToOpen}}tree/{{pathToOpen}}{{/if}}"
    requireSubdomain: false
  supportedFileExtensions: [ ".ipynb" ]
  title: "JupyterLab"
  iconUrl: "/assets/images/workspace-logos/jupyterlab.svg"
  start: [  "/var/opt/workspaces/Jupyterlab/" ]
    internalPath: "/{{ownerUsername}}/{{projectName}}/{{sessionPathComponent}}/{{runId}}/{{#if pathToOpen}}tree/{{pathToOpen}}{{/if}}"
    port: 8888
    rewrite: false
    requireSubdomain: false
 title: "vscode"
 iconUrl: "/assets/images/workspace-logos/vscode.svg"
 start: [ "/var/opt/workspaces/vscode/start" ]
    port: 8888
    requireSubdomain: false
  title: "RStudio"
  iconUrl: "/assets/images/workspace-logos/Rstudio.svg"
  start: [ "/var/opt/workspaces/rstudio/start" ]
    port: 8888
    requireSubdomain: false

(Optional) Persist MATLAB Preferences and Add-ons between sessions

In order to persist your MATLAB Preferences and Add-ons between Domino sessions, you can define a Post Run Script to automatically copy them to your Project Files when you Stop and Sync a session, and define a Pre Run Script to copy them from your Project Files into the locations MATLAB will recognize at the start of subsequent sessions.

Put the following lines into your Pre Run Script.

if [ -d /mnt/matlab-addons ]; then
    mkdir -p /home/ubuntu/Documents/MATLAB/SupportPackages/$MATLAB_VERSION/
    rsync -r /mnt/matlab-addons/ /home/ubuntu/Documents/MATLAB/SupportPackages/$MATLAB_VERSION
if [ -d /mnt/matlab-preferences/$DOMINO_STARTING_USERNAME ]; then
    mkdir -p /home/ubuntu/.matlab/$MATLAB_VERSION/
    rsync -r /mnt/matlab-preferences/$DOMINO_STARTING_USERNAME/ /home/ubuntu/.matlab/$MATLAB_VERSION

Put the following lines into your Post Run Script.

if [ -d /home/ubuntu/Documents/MATLAB/SupportPackages/$MATLAB_VERSION]; then
    mkdir -p /mnt/matlab-addons
    rsync -r /home/ubuntu/Documents/MATLAB/SupportPackages/$MATLAB_VERSION/ /mnt/matlab-addons
if [ -d /home/ubuntu/.matlab/$MATLAB_VERSION]; then
    mkdir -p /mnt/matlab-preferences/$DOMINO_STARTING_USERNAME
    rsync -r /home/ubuntu/.matlab/$MATLAB_VERSION/ /mnt/matlab-preferences/$DOMINO_STARTING_USERNAME

Note that these scripts will save add-ons per project, so that any collaborators launching a workspace in the same project will have the same add-ons. For preferences, however, they will be saved per user in the project so that each user can have a different set of preferences.

(Optional) Generate a startup script for proxy settings

If your company uses a proxy to connect to external networks, you may already have lines like the following in many of your Compute Environment Dockerfiles:

ENV http_proxy='http://someusername:[email protected]:80'
ENV https_proxy='http://someusername:[email protected]:80'
ENV HTTP_PROXY='http://someusername:[email protected]:80'
ENV HTTPS_PROXY='http://someusername:[email protected]:80'

Without setting the proxy information in MATLAB as well, you may not be able to connect to external networks from MATLAB (e.g. for downloading community Add-ons). Proxy information can be set manually in MATLAB under Preferences -> Web, and these will be persisted across sessions if the Pre and Post Run Scripts from the previous section are included in your environment.

Alternately, you can define a startup.m file in your project to ensure the proxy settings are correct at every launch of MATLAB. The file would look something like the following.

% This startup file was created from the environment pre-run script, to set proxy settings for MATLAB
disp('Setting proxy configuration via startup.m file')

Put the following lines into your Pre Run Script to automatically generate such a file in any project where it does not exist, whenever this Compute Environment is used to launch a session. (Omit the Authentication, Username, and Password lines if your proxy does not use them.)

if [ ! -f /mnt/startup.m ]; then
    echo "% This startup file was created from the environment pre-run script, to set proxy settings for MATLAB" > /mnt/startup.m
    echo "disp('Setting proxy configuration via startup.m file')" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setUseProxy(true)" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setProxyHost('')" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setProxyPort('80')" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setUseProxyAuthentication(true)" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setProxyUsername('someusername')" >> /mnt/startup.m
    echo "com.mathworks.mlwidgets.html.HTMLPrefs.setProxyPassword('password123')" >> /mnt/startup.m

Build and Test the Environment

Click Build when you have finished editing the above sections. You will be redirected to the Revisions page for the environment.

If the new revision builds successfully, you are ready to test! Go to the Project Settings for a project where you wish to use MATLAB and change the Compute Environment to use this new environment; once you do, you should see a MATLAB icon appear as an option for Workspaces in that project.


See the Troubleshooting section below for information on known issues and frequently encountered problems if anything does not work as expected.


GPU functionality does not work as expected

The most common problem with GPU functionality is not having the correct NVIDIA driver version for your environment configured in your Hardware Tier. The following shell command should print some information about the GPU driver versions so you can verify it with the compatibility tables linked in the Prerequisites section.

>> !nvidia-smi
Wed May 13 00:00:16 2020
| NVIDIA-SMI 440.64.00    Driver Version: 440.64.00    CUDA Version: 10.2     |
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|   0  Tesla V100-SXM2...  Off  | 00000000:00:1B.0 Off |                    0 |
| N/A   39C    P0    50W / 300W |      0MiB / 16160MiB |      0%      Default |
|   1  Tesla V100-SXM2...  Off  | 00000000:00:1C.0 Off |                    0 |
| N/A   41C    P0    50W / 300W |      0MiB / 16160MiB |      0%      Default |
|   2  Tesla V100-SXM2...  Off  | 00000000:00:1D.0 Off |                    0 |
| N/A   40C    P0    52W / 300W |      0MiB / 16160MiB |      0%      Default |
|   3  Tesla V100-SXM2...  Off  | 00000000:00:1E.0 Off |                    0 |
| N/A   40C    P0    54W / 300W |      0MiB / 16160MiB |      4%      Default |
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|  No running processes found                                                 |

MATLAB workspace fails to launch

License configuration problems

License issues are the most common cause of problems launching a MATLAB workspace. To debug, start a Jupyter or RStudio workspace (still using the MATLAB environment) and open a Terminal. Check if your license server information has been correctly entered into the network.lic file, in the correct part of the MATLAB directory structure (i.e. matching your MATLAB version):

$ which matlab
$ cat /usr/local/MATLAB/R2019b/licenses/network.lic

If that contains the license server information you expect, but there are still problems, you can use the lmutil utility to check that the license server is reachable and contains the correct information.

$ lmutil lmstat -a -c

It should output information on the licenses being managed by that license server, including the MATLAB licenses.

Advanced troubleshooting

The workspace launch process for MATLAB respects several environment variables related to logging, which may help you debug more obscure or advanced problems. You can set these as project-level environment variables, similar to how you would set environment variables for secure credential storage, to enable toggling them on or off without having to edit the Compute Environment.

  • WS_LOGGING=[MATLAB]|ALL|DEBUG. By default, only the MATLAB logs are shown.

    • ALL shows logs for the underlying screen management xterm and xpra.

    • DEBUG shows everything from ALL, and activates a flag to show all commands.

  • TTY_MODE=[disabled]|PRE|POST. Runs ttyd before or after the workspace. It’s a terminal that runs in a browser so you can easily inspect things.

    • PRE will run ttyd before the workspace launch.

    • POST will run ttyd after the workspace launch fails (if it fails).

  • START_LOGGING=[false]|true. Increases logging verbosity in certain stages.

MATLAB workspace is laggy

In poor network conditions you may notice some lag in typing and general interactions with the MATLAB UI. This is to be expected in certain circumstances. Other common Domino workspaces like Jupyter or RStudio use browser-based IDEs, while this MATLAB environment is running a (Linux) desktop version of MATLAB in a remote desktop style interface. This results in more sensitivity to slow network conditions than a browser-based IDE.

For these situations, if you encounter them frequently, you may find it useful to install the Domino CLI on your local machine to facilitate editing files locally, then syncing them to Domino.

Keyboard shortcuts for copy/paste do not work

MATLAB in Domino runs the Linux version of MATLAB, which uses the “Emacs” set of keyboard shortcuts by default. To enable keyboard shortcuts Ctrl+C and Ctrl+V for copy and paste, go to Preferences -> Keyboard -> Shortcuts and change this from “Emacs” to “Windows”. See the MATLAB help for more details.

Connection error when downloading Add-ons or using urlread

If you get network errors when downloading Add-ons or using urlread to download files, it may be due to proxy settings. See the (Optional) Generate a startup script for proxy settings section above for options for setting your proxy in MATLAB either within the current session or more globally.

Toolbox is not available

A selection of Toolboxes is pre-installed in each MATLAB base image, but this may not include every Toolbox you have on your local installation. You can see the list of Toolboxes by running the ver command within MATLAB, and the list is also documented for each base image. We may release more base images in the future, with different selections, and you can contact your Domino account team with any specific requests for Toolboxes to include.

In addition to having the Toolbox installed in the base image, you must have an available license for using it on your license server.

Known Issues and Release Notes

If your problem is not listed in this FAQ, it may be worth checking the release notes for the base image you are using. Especially if your environment is built on an older image tag, checking the release notes of newer images may give you a quick answer about whether rebuilding on the most current image will help.

MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See for a list of additional trademarks.