Create a workspace

How to create a workspace

To create a workspace you need to select few options including, workspace name, resource, image, and a few advanced settings.
The overall options for creating a workspace
Put the asterisk mark(*) on the required option

Workspace Name*

Once you start to create a new workspace, the default workspace name will be randomly generated. Specify a good name to remember.


If you successfully added your custom cluster, then you can choose the cluster between the Managed Cluster and the Custom Cluster. The managed cluster always on the cloud vendor server, whereas the custom cluster could be either on the cloud server or on the on-premise server.
Managed Cluster
Custom Cluster
For the Managed Cluster, you should choose the type of resource that the container will use. Select the resource among the dropdown option.
Use 'v1.cpu-2.mem-6' resource on the managed cluster
For the Custom Cluster, you should choose the processor type and specify the resource requirements. The workspace will be automatically assigned to an available node according to the given resource requirements.
Run workspace on any node that satisfies the specified resource spec


You can choose the Docker image that the workspace container will use. There are two types of images: the Managed Image and the Custom Image. Select the Docker image type that you want to run on the workspace container.
Managed Image
Custom Image
For the Manged Image, you can simply select such an option, then the image managed by SavviHub will be used in default. You can run Jupyter services on the managed image.
Select the managed docker image
Custom Image is NOT managed by SavviHub. Instead, it allows you to pull images from either Docker Hub or AWS ECR.

Public image

To pull images from the public Docker registry, you can simply pass the image URL as the below example.
Use the custom notebook image from the Docker Hub

Private image

To pull images from the private Docker registry or the private AWS ECR, you should integrate your credentials in organization settings first. Then check the private image checkbox and select the credentials you have just integrated. Below is an example of a private image from the AWS ECR.
Use the custom AWS ECR private image with the AWS credentials
Debian based images are compatible.

Advanced Setting

You can choose the disk size and customize port settings on the advanced settings. Disk size is 100 GiB by default. Also, the 8888 port is used by Jupyter, and the 22 port is used by ssh by default.
Init script is a shell script that runs every time the workspace starts. Because /home/vessl is the only persistent directory, packages you installed outside the home directory may reset on stop & start. In this case, you can fill init script with install commands such as apt-get update && apt-get install ripgrep -y.
The default advanced settings
Last modified 4mo ago