yungsang / coreos-vboxguest Goto Github PK

Error Screen:

D:\docker-host>git clone https://github.com/YungSang/coreos-vboxguest.git
Cloning into 'coreos-vboxguest'...
remote: Counting objects: 30, done.
remote: Total 30 (delta 0), reused 0 (delta 0), pack-reused 30
Unpacking objects: 100% (30/30), done.
Checking connectivity... done.

D:\docker-host>ls
coreos-vagrant coreos-vboxguest

D:\docker-host>cd coreos-vboxguest

D:\docker-host\coreos-vboxguest>ls
Dockerfile README.md Vagrantfile installer

D:\docker-host\coreos-vboxguest>vagrant up
Bringing machine 'coreos-vboxguest' up with 'virtualbox' provider...
==> coreos-vboxguest: Box 'yungsang/coreos-alpha' could not be found. Attempting to find and install...
coreos-vboxguest: Box Provider: virtualbox
coreos-vboxguest: Box Version: >= 1.3.1, <= 1.4.0
==> coreos-vboxguest: Loading metadata for box 'yungsang/coreos-alpha'
coreos-vboxguest: URL: https://atlas.hashicorp.com/yungsang/coreos-alpha
==> coreos-vboxguest: Adding box 'yungsang/coreos-alpha' (v1.4.0) for provider: virtualbox
coreos-vboxguest: Downloading: https://atlas.hashicorp.com/yungsang/boxes/coreos-alpha/versions/1.4.0/providers/virtualbox.box
coreos-vboxguest: Progress: 100% (Rate: 683k/s, Estimated time remaining: --:--:--)
==> coreos-vboxguest: Successfully added box 'yungsang/coreos-alpha' (v1.4.0) for 'virtualbox'!
==> coreos-vboxguest: Importing base box 'yungsang/coreos-alpha'...
==> coreos-vboxguest: Matching MAC address for NAT networking...
==> coreos-vboxguest: Checking if box 'yungsang/coreos-alpha' is up to date...
==> coreos-vboxguest: Setting the name of the VM: coreos-vboxguest_coreos-vboxguest_1438003513754_46596
==> coreos-vboxguest: Preparing SMB shared folders...
coreos-vboxguest: You will be asked for the username and password to use for the SMB
coreos-vboxguest: folders shortly. Please use the proper username/password of your
coreos-vboxguest: Windows account.
coreos-vboxguest:
coreos-vboxguest: Username:
coreos-vboxguest: Password (will be hidden):
==> coreos-vboxguest: Clearing any previously set network interfaces...
==> coreos-vboxguest: Preparing network interfaces based on configuration...
coreos-vboxguest: Adapter 1: nat
coreos-vboxguest: Adapter 2: hostonly
==> coreos-vboxguest: Forwarding ports...
coreos-vboxguest: 22 => 2222 (adapter 1)
==> coreos-vboxguest: Running 'pre-boot' VM customizations...
==> coreos-vboxguest: Booting VM...
==> coreos-vboxguest: Waiting for machine to boot. This may take a few minutes...
coreos-vboxguest: SSH address: 127.0.0.1:2222
coreos-vboxguest: SSH username: core
coreos-vboxguest: SSH auth method: private key
coreos-vboxguest: Warning: Connection timeout. Retrying...
coreos-vboxguest: Warning: Connection timeout. Retrying...
coreos-vboxguest: Warning: Connection timeout. Retrying...
coreos-vboxguest:
coreos-vboxguest: Vagrant insecure key detected. Vagrant will automatically replace
coreos-vboxguest: this with a newly generated keypair for better security.
coreos-vboxguest:
coreos-vboxguest: Inserting generated public key within guest...
coreos-vboxguest: Removing insecure key from the guest if its present...
coreos-vboxguest: Key inserted! Disconnecting and reconnecting using new SSH key...
==> coreos-vboxguest: Machine booted and ready!
GuestAdditions versions on your host (4.3.30) and guest (4.2.0) do not match.
The guest's platform is currently not supported, will try generic Linux method...
Copy iso file C:\Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 4.3.30 - guest version is 4.2.0
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.30 Guest Additions for Linux............
VirtualBox Guest Additions installer
Copying additional installer modules ...
ln: failed to create symbolic link '/usr/bin/VBoxClient': Read-only file system
ln: failed to create symbolic link '/usr/bin/VBoxControl': Read-only file system
ln: failed to create symbolic link '/usr/sbin/VBoxService': Read-only file system
ln: failed to create symbolic link '/usr/sbin/vbox-greeter': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxGuestAdditions': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGL.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLarrayspu.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLcrutil.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLerrorspu.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLfeedbackspu.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLpackspu.so': Read-only file system
ln: failed to create symbolic link '/lib64/VBoxOGLpassthroughspu.so': Read-only file system
ln: failed to create symbolic link '/usr/lib/VBoxGuestAdditions': Read-only file system
ln: failed to create symbolic link '/usr/share/VBoxGuestAdditions': Read-only file system
add_symlink: link directory /usr/src does not exist
Installing additional modules ...
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
Unable to determine your Linux distribution
An error occurred during installation of VirtualBox Guest Additions 4.3.30. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.

==> coreos-vboxguest: Configuring and enabling network interfaces...
==> coreos-vboxguest: Mounting SMB shared folders...
coreos-vboxguest: D:/docker-host/coreos-vboxguest => /tmp/vagrant
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t cifs -o uid=id -u core,gid=getent group core | cut -d: -f3,nolock,vers=3,udp,sec=ntlm,username=,pass=PASSWORDHIDDEN ///13a343f9ba1be7f
25493a524a4d12d56 /tmp/vagrant
mount -t cifs -o uid=id -u core,gid=id -g core,nolock,vers=3,udp,sec=ntlm,username=,pass=PASSWORDHIDDEN ///13a343f9ba1be7f25493a524a4d12d56 /tm
p/vagrant

The error output from the last command was:

mount: wrong fs type, bad option, bad superblock on ///13a343f9ba1be7f25493a524a4d12d56,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount. helper program)

   In some cases useful info is found in syslog - try
   dmesg | tail or so.