domino logo
Tech Ecosystem
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 PortfolioProject Goals in Domino 4+Upload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCommentsCompare File Revisions
Revert Projects and Files
Revert a FileRevert a Project
Archive 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 StorageUse Apache Airflow with Domino
Scheduled Jobs
Domino Workspaces
WorkspacesUse Visual Studio Code in Domino WorkspacesPersist RStudio PreferencesAccess Multiple Hosted Applications in one Workspace SessionUse Domino Workspaces in Safari
Spark on Domino
On-Demand Spark
On-Demand Spark OverviewValidated Spark VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
External Hadoop and Spark
Hadoop and Spark OverviewConnect 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 DominoRun Local Spark on a Domino ExecutorUse PySpark in Jupyter WorkspacesKerberos Authentication
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 ProductionExport Model Image
Publish a Web Application
Cross-Origin Security in Domino web appsApp 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
Advanced User Configuration Settings
User 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 SupportSupport Bundles
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Domino Reference
>
Domino Workspaces
>
Use Visual Studio Code in Domino Workspaces

Use Visual Studio Code in Domino Workspaces

Some Domino standard environments support launching Visual Studio Code (VSCode) in interactive Workspaces. VSCode is an open-source multi-language editor maintained by Microsoft. Domino can serve the VSCode application to your browser with the power of code-server from Coder.com.

Prerequisites

VSCode support is available in the latest versions of the Domino standard environments:

Domino Analytics Distribution for Python 2.7
  • quay.io/domino/base:Ubuntu18_DAD_Py2.7_R3.5-20190501

Domino Analytics Distribution for Python 3.7
  • quay.io/domino/base:Ubuntu18_DAD_Py3.7_R3.5-20190501

Domino Analytics Distribution for Python 3.6
  • quay.io/domino/base:Ubuntu18_DAD_Py3.6_R3.5-20190501

Launch a VSCode workspace

When using a VSCode-equipped Domino environment you can launch VSCode from the Workspaces Dashboard just as you would launch an RStudio or Jupyter workspace.

vscode workspace launch

Option 1: Launch VSCode directly

You can launch VSCode directly from the Workspaces dashboard or Quick Action menu, the same way you would launch RStudio or Jupyter.

Screen Shot 2019 05 16 at 9.42.26 AM

If launched this way, your Workspace will open with the Domino controls around a VSCode editor. You can work with your project files in VSCode, and commit and sync with the Domino Workspace UI as normal.

Screen Shot 2019 05 16 at 9.49.29 AM

Option 2: Launch VSCode from JupyterLab

In VSCode-equipped environments, you will also find VS Code IDE as a notebook option in JupyterLab.

Screen Shot 2019 05 16 at 9.43.16 AM

If launched this way, JupyterLab will open a new tab that will serve the VSCode application. This editor is running in the same Domino Run container as your JupyterLab application. However, the VSCode tab will not show the Domino Workspace controls. If you want to sync, commit, or stop your Workspace after working in VSCode, you must do so from the JupyterLab tab.

Install VSCode extensions

You can install VSCode extensions in the following ways:

  1. Use the pre-run script.

  2. Use VSCode’s Extensions Manager.

Use the pre-run script
  1. Go to the environment.

  2. Click Edit Environment.

  3. In Pre Run Script, paste the following:

    code-server --install-extension <extension-name> --extensions-dir ${HOME}/.local/share/code-server/extensions
  4. Click Build.

Use VSCode’s Extensions Manager

Use the VSCode’s Extensions Manager to install extensions from the marketplace. You must build the extensions in your environment to make them available in every new VSCode workspace.

Screen Shot 2019 05 16 at 10.01.25 AM

  1. Find the extension you want to install in the Visual Studio Marketplace. For example, install the scala-lang extension.

  2. Microsoft obscures the download URL for the extension by default. Open your browser’s development tools, then click Download extension.

    Screen Shot 2019 05 16 at 10.11.24 AM

  3. Get the download URL for the extension from the request details in your browser’s development tools. It ends with /vspackage. Copy this URL.

    Screen Shot 2019 05 16 at 10.14.00 AM

  4. In Domino, create a new environment. As the base image, use one of the VSCode-equipped Domino Standard Environments, listed in the prerequisites.

    Screen Shot 2019 05 16 at 10.17.42 AM

  5. Add the following instructions to your environment’s Dockerfile. Replace the folder names and example /vspackage URL with the extension URL you retrieved previously. These commands download the extension, extract the required files, and adds them to the appropriate folder.

RUN apt-get update
RUN apt-get install -y bsdtar
RUN mkdir -p /home/ubuntu/.local/share/code-server/extensions/ms-python.python-2019.3.6558
RUN cd /home/ubuntu/.local/share/code-server/extensions/ms-python.python-2019.3.6558
RUN curl -JL https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2019.3.6558/vspackage | bsdtar -xvf - extension

RUN cd /home/ubuntu/.local/share/code-server/extensions/ms-python.python-2019.3.6558/extension/ && mv * ../
RUN chown ubuntu:ubuntu /home/ubuntu/.local/share/code-server/
  1. Click Build. After a successful build, you can use this new environment to launch VSCode Workspace sessions with the extensions already installed.

Install VSCode to older environments

You can add VSCode to some older environments by adding the following to your compute environment. The base environment must be 2018-05-23 or newer.

  1. Add the following to your compute environment docker file instructions:

    #note: Make sure you are using the latest release if you'd like the latest version of the workspaces
    #https://github.com/dominodatalab/workspace-configs/releases
    
    RUN cd /tmp && wget https://github.com/dominodatalab/workspace-configs/archive/2019q2-v1.3.zip && \
    unzip 2019q2-v1.3.zip && cp -Rf workspace-configs-2019q2-v1.3/vscode /var/opt/workspaces/vscode && \
    rm -rf /var/opt/workspaces/workspace-logos && \
    rm -rf /tmp/workspace-configs-2019q2-v1.3
    
    RUN \
    chmod +x /var/opt/workspaces/vscode/install && sleep 2 && \
    /var/opt/workspaces/vscode/install
  2. Add the following to your compute environment’s Pluggable Workspace Tools:

vscode:
 title: "vscode"
 iconUrl: "https://raw.github.com/dominodatalab/workspace-configs/develop/workspace-logos/vscode.svg?sanitize=true"
 start: [ "/var/opt/workspaces/vscode/start" ]
 httpProxy:
    port: 8888
Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.