With my Datalab instance, I can't run my script because the Kernel is dead and i don't have any option to select Python3 or Python 2.
I restarted the session and tried also to restart the VM also, but nothing changed, the Kernel option is still unavalaible to choose!
Can you help please?
There's an issue when connecting to Datalab from the Cloud Shell. You can workaround this issue by connecting to the instance without Cloud Shell and create a tunnel on port 8080 to display the Datalab UI on your machine.
In addition, I suggest switching to AI Platform Notebooks which provides an easy to use managed JupyterLab VM similar to Datalab and don't have this issue. Here's the quickstart to create a notebook.
Related
Let me give the necessary context:
Security group details for Instance:
Jupyter Notebook Config File Snapshot:
When I run jupyter notebook this is what I get
And I cant connect to the Instance as I am getting this error:
Not sure what I am missing out or doing wrong. Any help would be appreciated.
You can run it in a headless mode, without browser:
jupyter notebook --no-browser
Then you can access it from your local workstation. Preferably over ssh tunnel for security reasons, rather then directly.
For example, in Linux VM instances we can use gcloud beta ssh command to run commands remotely by downloading ssh keys using gcp credentials
Similarly, I am looking for running scripts on Windows VM instance remotely without doing RDP to an instance.
Can someone point to a solution for this problem?
If you have a Windows workstation with PowerShell, you can connect to your Windows Server instances through a remote PowerShell session. This process is similar to connecting to a Linux instance using SSH. Please review "Connecting to Windows instances using the PowerShell terminal"
https://cloud.google.com/compute/docs/instances/connecting-advanced#powershell
I have a Windows Server 2012 instance running on Gcloud Compute Engine. Just yesterday I was installing an antivirus and the program installation stopped.
I aborted the installation and rebooted the instance, but I was unable to access again to the instance. I can't figure out any way to access this instance any more.
It doesn't appear there is a console. Is there a way to force Windows into safe mode during boot time from gcloud? Any suggestions?
Thanks,
Jeremy
I can set up a ipython/jupyter notebook server on aws ec2 by following this tutorial, it starts the remote server by entering $jupyter notebook in the local terminal.
However I also saw a pre-configured community AMI graphlab-create, which will run the remote server without the need of a Linux/Unix ssh client at all.
I'm wondering how that could be realized, since some students may not have an access to a linux/unix system. Any hint is appreciated.
Using windows is not an issue. I hooked up to my notebook in AWS from my home computer. I have Windows 10.
You can link up to AWS using putty.
I am using a Ubuntu AMI.
Once you have a terminal open you simply follow the instruction you gave in your link
It worked like a charm for me.
For testing of automated OS deploy on a hardware cluster, I need Vagrant to create few VMs without OS installed, with just network boot enabled.
I succesfully created base box image and configured boot order with Vagrant.
Problem is that Vagrant dies after waiting for VM to boot (which it doesn't, because it has nothing to boot), trying to set up ssh forwarding, shared folders etc.
Is there any way I can tell Vagrant to just power on the machine and not try to configure or boot it?
Vagrant's idea is to manage already installed boxes. It has some requirements for them. SSH or other login access is a fundamental one.
If you just want to spin up a VirtualBox VM, you can call VBoxManage etc. directly.