Run RStudio Server on Windows Subsystem for Linux - rstudio

I installed RStudio Server on the Linux Subsystem on my Windows 10 machine, but my browser won't connect to http://localhost:8787. When I run sudo rstudio-server verify-installation, I get the error Unable to connect to Upstart.
I know WSL doesn't support Upstart or systemd; how can I run RStudio Server?

I can start RStudio Server without Upstart or systemd by running exec /usr/lib/rstudio-server/bin/rserver at the Bash prompt.

Related

Windows Subsystem for Linux has no installed distributions for local administrator

I have successfully installed WSL 2 and Ubuntu on my windows machine. If I start PowerShell and type bash it successfully starts bash.
However if I run PowerShell as Administrator and type bash I get the following message:
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Worst part is that I'm pretty sure this worked yesterday(!)

Excpetion when installing gofabric8 in Windows Subsystem for Linux

In my system I have enabled the Windows Subsystem for Linux(WSL) and installed Ubuntu on Windows 10.
https://github.com/fabric8io/fabric8-platform/blob/master/INSTALL.md
On top of the WSL, I was trying to install the fabric8 from the scratch with the Minishift using instructions for Ubuntu in the above link and while running the below command, getting error stating that "No User home environment variable found for os windows"
gofabric8 start --minishift --package=system --namespace fabric8
Note: Before running the above commands, I have setup libvirt and qemu-kvm in my WSL
I had the same problem installing fabric8 on Windows. A look into the sourcecode reveals, you need to define a HOME environment variable. In windows CMD try
set HOME=C:\Users\yourHome
That worked for me

Opening spyder in Windows subsystem for Linux fails

I've installed spyder through the Windows Subsystem for Linux system and am having problems opening the program from the command line (command line of Bash on Ubuntu on Windows application on Windows)
spyder
error given:
Spyder: cannot connect to X server
How do I fix this?
"cannot connect to X server" means you don't have running an x server. You can download one here https://sourceforge.net/projects/vcxsrv/
After installing and running VcxSrv then you can type on bash DISPLAY=:0 spyder

Xming window not showing (Solaris/Windows)

I am trying to launch an install wizard window from a Solaris 9 system on my Windows 7 host to install Sybase ASE but the window won't show.
I am using Putty, with X11 forwarding enabled, and Xming on my Windows host. I am getting no error from the Solaris system. It just says Running InstallShield Wizard... and on my Windows, when I try to exit Xming it says There are currently 1 clients connected.
So clearly, my Solaris is connected to Xming, but I can't see the window.
You have to allow the solaris server to connect to the XMING config file by adding the server IP Address in the file X0.hosts (XMING install folder) then restart the XMING server on your PC. If it still does not work, try running "xhosts +" from Solaris command and export DISPLAY=your_server_IP_Address:0.0.

How to initialize and run Docker on windows?

I have Docker installed on Windows 7 platform. However when I try to run boot2docker start, the console gives me:
Failed to get machine 'boot2docker-vm': machine does not exist.
Ok, so I try to initialize the machine: boot2docker init. What now happens is even though I have the ISO image on the same path as docker, it tries to download a new image (and then fails to do so).
I uninstalled both OracleVM and GIT before installing them with boot2docker bundle as advised on Docker forums, but now I don't know how to proceed.
I had the same problem on a Windows 7 64 bit system when I installed the entire boot2docker package. It seems that running the solely 64-bit based boot2docker image from a 32-bit OS image (e.g. created by Virtualbox) does not work.
The solution for me was
to activate Intel Virtualisation Technolologies in my BIOS
(Lenovo X61 for me). Note that the settings can be found either
under CPU or Security.
choose a 64 bit OS version in VirtualBox and boot in with the
image obtained by boot2docker.
In case you're trying to do this now
For Windows 10 64-bit: Pro, Enterprise, or Education (Build 15063 or later), follow the instructions to install Docker Desktop here https://docs.docker.com/docker-for-windows/install/.
If you have Windows systems that do not meet the requirements of Docker Desktop for Windows(in my case Microsoft Windows 10 Home Single Language), you can install Docker Toolbox by following the instructions here https://docs.docker.com/toolbox/toolbox_install_windows/.
boot2docker does not support sharing directories on Windows IIRC. The way I run Docker on windows is:
install VirtualBox
install Vagrant
create a directory (let's say c:\vm\docker)
download this Vagrantfile and save it under c:\vm\docker\Vagrantfile
open a DOS command prompt
go to the directory cd c:\vm\docker
start the VM vagrant up and wait for it to install, start up and get provisionned
connect to the VM vagrant ssh
play with docker docker images, etc
Also you might want a real console instead of using the DOS command prompt:
install Git Bash for Windows
install Console
setup Console to use Git Bash (see this guide)
use Console to run the vagrant up and vagrant ssh commands

Resources