WSL - Ubuntu - Install Travis CLI

[rgleason]

Have tried this twice with Norton360 Off, setting up a VM Ubuntu 18,
It seems to hang up here creating the virtual disk of about 40gb
I'll wait another hour.
It may look easy but it aint.
https://itsfoss.com/install-linux-in-virtualbox/
https://brb.nci.nih.gov/seqtools/ins....html#createvm

[rgleason]

Have done post #28 Thanks very much.


How about this piece of work? WSL is setting HyperV stuff causing troubles with VirtualBox?
https://github.com/Microsoft/WSL/issues/2850


Is improved security at the core part of the issue?
https://techcommunity.microsoft.com/...rm/td-p/167303


So now I think it is one or the other, WSL or VirtualBox.

[rgleason]

Got Ubuntu installed the third time. Would get lost in never never land. It finally completed properly. I think it had to do with the virtual disk I think.


sudo apt-get update 5mb
sudo apt-get install ruby 7.5mb +23.8mb

sudo apt-get install gem 27.8 mb
sudo gem update <--- errors in this!! Will attach tomorrow.

[Canne]

Originally Posted by rgleason

Have tried this twice with Norton360 Off, setting up a VM Ubuntu 18,
It seems to hang up here creating the virtual disk of about 40gb
I'll wait another hour.
It may look easy but it aint.

Dear Rick, it is easy, just that you need patience to allow the convenience function to make its work: we have asked Dynamic allocation of disk from Vbox, right? We start from zero. When the installer of Ubuntu starts on this new instance provided by Vbox, it needs chunks of disk. Big chunks of disk. With Dynamic allocation, it needs to ask from Windows that free space. Since your system has (probably) some mileage, the free space is distributed here and there and it takes time for Windows to allocate the required disk space, give it back to Vbox, who give it to the Ubuntu installer.

If you would have selected static allocation of disk (a fix size disk) that time would have been taken at that moment, before Ubuntu install starts. If you have a brand new host system, this step, however would be fast (disk sectors are homogeneous).

Norton 360 off or on does not help at all this process since it is totally local operation.

[Canne]

Originally Posted by rgleason

How about this piece of work? WSL is setting HyperV stuff causing troubles with VirtualBox?
https://github.com/Microsoft/WSL/issues/2850

Let's look at this first from small scale: yes, there is a risk, but since the symptoms appears to be "VT-x is disabled", if that would be the case, your Vbox would not run your Ubuntu. Now it does, so don't worry.

The risk may get realized when you upgrade to WSL2 later this summer (I know you will!).

Maybe you are interested in the big picture: Microsoft servers are not selling very well but Linux derivates are dominating. To avoid their existing, big company client base to switch from MS servers to Linux boxes, they make them more attractive by being "Linux compatible". They are not eager to support other virtual managers but their own HyperV, either. What does this mean to average Joe? For winduzien it means short sighted satisfaction. For linuxien it means that Canonical Inc. is trying to make money and they have horribly butchered Linux by mangling it with the namespace of Windows. I am not sure that Linux developers will appreciate and in long term the MS solution will decay and fade away (IMHO).

What the average Joe can do? Not much, except switching to Linux (not necessarily Ubuntu but to its forks) and run Windows as virtual instance as a guest operating system (I've been doing that for years, so that I have even Windows XP images which are still booting, even if I have changed hardware meanwhile).

[Canne]

Originally Posted by rgleason

sudo apt-get install gem 27.8 mb
sudo gem update <--- errors in this!! Will attach tomorrow.

Where you did get the need to update? In my record for a successful installation on 18.04LTS WSL here:
http://www.cruisersforum.com/forums/...ml#post2915207
I did not had such a step to execute. What procedure you are following, mine or something else?

[rgleason]

Trying to follow yours. Now I have added Vbox guest additions, and tried to get shared folders working, and enable the clipboard and drag and drop. I have installed guest additions twice and rebooted a number of times, shutdown vbox, reopened, etc. and I cannot seem to get the shared folder to appear in ubuntu.

I want to copy a file I saved of the terminal output back to windows, so I can attach it here.

NOTE: I did not install the full version of Ubuntu, I choose not to install Office programs and Media. Is vbox extensions depending on that for shared folders??


When I enter this into ubuntu terminal $ sudo adduser rgleason vboxsf
[sudo] password for rgleason:

adduser: the group 'vboxsf' does not exist.

I have used C:\Users\Rick\Documents\1-Ubuntu as the shared folder in VirtualBox and have selected Full access, Auto mount, and Mount Point: "G:" Checked Permanent. This shows up under the Machine Folders for the Ubuntu VM in Vbox.

Yet, I cannot copy text from guest Ubuntu to host Win and I cannot access the shared folder in Ubuntu!

[rgleason]

Tried turning on Sharing setting in Ubuntu. No dice.


In File manager > Other locations > Windows Network


Click -- Failed to retrieve Windows share list.


Using Terminal


mount -t vboxsf 1-ubuntu G:
mount: only root can use "...types" option


sudo mount -t vboxsf 1-ubuntu G:
pw
mount : G:: mount point does not exist


sudo mount -t vboxsf 1-ubuntu
moutn: 1-ubuntu cant find in /etc/fstab


----


mkdir Share
sudo mount -t 1-Ubuntu ~/Share/
wrong fs type, superblock, bad option, bad superblock on 1-Ubuntu, missing code page or other error.

[rgleason]

sudo mount -t vboxsf 1-C:/Documents/Ubuntu/ ~/Share/
wrong fs type, superblock, bad option, bad superblock on C:/Documents/1-Ubuntu/, missing code page or other error.


lsmod | grep vboxguest
303104 1 vboxsf

[rgleason]

This is f____ ridiculous. I don't think vbox guest extensions is installed. Is it because I did not choose to install the full and complete version of Ubuntu 18.04LTS with Office Programs and Media? -There is no media directory, in devices I see the VBOX.iso but not the Guest extensions.iso -There is no nux directory... the list goes on, but something is installed for guest extensions, just not what we need I guess.


Should I just go back, make a new VM and install the full version?


All of this to run Travis ...I am almost at the point of saying screw it and go sailing.

[rgleason]

Petri,
When the virtual file was created, did it clean up the segmentation at all?
Reason I ask, is if I remove the current VM Ubuntu and the virtual disk, and then immediately recreate and make a new VM with the same 20gb will it install faster?

[Canne]

Originally Posted by rgleason

...if I remove the current VM Ubuntu and the virtual disk, and then immediately recreate and make a new VM with the same 20gb will it install faster?

I don't think that reinstalling Linux does not resolve anything...

... But if you do, it is better install it in using the same virtual guest instance you have already created - to answer your question, if you delete the virtual instance, its disk reservations on Windows file system will be removed and yes, the next installation will take again longer time.

So I would say: don't do it. You have invested time on this, let's build on your work done until now.

Rick, aren't we deviating from our initial objective to get you a platform for Travis and to get you a Travis CLI ?

Can't we just finish with it - a minimum installation of Linux is all that we need for now.

After we have reached this objective we can go forward with Vbox extensions installation on guest OS, file system sharing, installation of opencpn, etc.

Forget about the shared folders for now. Can you cut from Ubuntu terminal and paste into Windows browser? If yes, that's enough and we should continue the procedure I have successfully executed (I hope it is not too late).
----
BTW, is there a browser in Linux? Maybe you can use simply that to chat with me?

[Canne]

Dear Rick, I hope that the sailing was good. Here's too hot for it and no wind, so as promised I installed for myself and on my Windows 10 Vbox 6 and repeated the procedure of WSL Travis CLI on it. One small exception apart it it the same on Vbox'ed miminal install Ubuntu 18.04.2LTS as it is was on WSL 18.04.LTS (http://www.cruisersforum.com/forums/...ml#post2915207). It is mainly in screenshots and thus on several posts.

This is what I used


I got 10GB of free disk on Win10 by emptying the trash and Windows 10 upgrade cache (it is really long to clean it). That I am going to use for the Travis CLI Ubuntu installation.


Let's start the installation


Memory should be increased from what suggested.


to be continued...

[rgleason]

This is helpful. Solves the main problem right now. Communication.

Originally Posted by Canne

1. if you do, it is better install it in using the same virtual guest instance you have already created - ok, thanks.

2. buildon work done -ok, but can't copy and paste or shared folders.
3. aren't we deviating from our initial objective to get you a platform for Travis and to get you a Travis CLI ? - nope
4. finish with a minimum installation of Linux. Ok
5. After reached this objective we can go forward with Vbox extensions installation on guest OS, file system sharing, installation of opencpn, etc. -Sure
6. Forget about the shared folders for now. -ok Can you cut from Ubuntu terminal and paste into Windows browser? yes!! . Browser in Linux? use to chat with me? - Firefox. Ubuntu is very slow but it works. This is a different way. Good.

[Canne]

... cont'd

About disks, I decided that 10 GB is enough, but I don't plan to install bells and whistles on this system which sole purpose is to provide Travis CLI. I would recommend that you start like the same way. When you want to expand your Linux testing to Linux, you can install a second instance which has, say 30 GB of disk.



You may notice that I opted for fixed disk size. I am pretty sure and know what to expect. I am not going to install much stuff here.

You can see actually the "disk" which is a one file in Windows. If you have a lot of disk space, that file can be continuous and thus much faster than on system with millions and millions of files already. But 10 GB should be not a problem even on my system, which has a 256 GB disk.


... to be continued ...