IssueTracker

An user is creating notebooks using GCloud so they can change the metadata during creation and set  use-websockets-shim to true [1]. This works when using image "common-cpu-notebooks-20200127" but not with "pytorch-1-3-cu100-notebooks-20191219" [2].

It looks there are differences in the "attempt-register-vm-on-proxy.sh" file that during creation changes or not the metadata. This can be checked by running "cat /opt/deeplearning/bin/attempt-register-vm-on-proxy.sh | grep -i shim" in both images, their output is different.

** Is there any plan to make the images more consistent so said metadata can be changed in all images?
** Could an option to change this directly in the UI or with a flag during creation be added?

[1] export IMAGE_FAMILY="common-cpu-notebooks" #image will be common-cpu-notebooks-20200127

export ZONE="europe-west1-b"

export INSTANCE_NAME="instance-common"

export INSTANCE_TYPE="n1-standard-1"

gcloud compute instances create $INSTANCE_NAME
--zone=$ZONE
--image-family=$IMAGE_FAMILY
--image-project=deeplearning-platform-release
--boot-disk-size=80GB
--scopes=https://www.googleapis.com/auth/cloud-platform 
--metadata="proxy-mode=project_editors,container=${CONTAINER}"

[2] export IMAGE_FAMILY="pytorch-1-3-cu100-notebooks" #image will be pytorch-1-3-cu100-notebooks-20191219

export ZONE="europe-west1-b"

export INSTANCE_NAME="instance-pytorch"

export INSTANCE_TYPE="n1-standard-1"

gcloud compute instances create $INSTANCE_NAME
--zone=$ZONE
--image-family=$IMAGE_FAMILY
--image-project=deeplearning-platform-release
--boot-disk-size=80GB
--scopes=https://www.googleapis.com/auth/cloud-platform 
--metadata="proxy-mode=project_editors,container=${CONTAINER}"