Reporting for launched xhyve #18

zchee · 2015-11-21T19:32:52Z

This thread is not issue thread. Post a report only.
See also Would you do me a favor?

OK, Running, Good, etc...
Anything will do.

johanneswuerbach · 2015-11-21T20:30:52Z

Hey, I would like to try the driver, but it seems to have a lot of dependencies https://github.com/zchee/docker-machine-xhyve#libguestfs (OSX Fuse, etc.). Mind uploading a binary?

zchee · 2015-11-21T21:21:51Z

@johanneswuerbach Thanks issue!

I can upload the binary, but the binary requests a libguestfs.dylib as a dynamic linking.
The reason, OS X does not support static build.
If remove the libguestfs, there are several problems.

Needs way to copy the userdata.tar to disk image before launch the xhyve
Give up use extfs Docker Backing Filesystem (will be using tmpfs. bad performance)

I know how to solve these without libguestfs, but I felt that pretty way used libguestfs.

If you are satisfied with tmpfs, I will make use tmpfs version binary from now.

BTW, I also have a problem in many of dependency.
I'm looking for a better way to make ext.4 disk image without a libguestfs.

Sorry terrible English :(

johanneswuerbach · 2015-11-21T21:47:26Z

I definitely see why you used libguestfs, but can't b2d auto-format the disk when it discovers an unformatted one? https://github.com/boot2docker/boot2docker/blob/master/rootfs/rootfs/etc/rc.d/automount#L13-L16

zchee · 2015-11-21T22:15:02Z

@johanneswuerbach I tried before. I don't remember so much...

But, docker-machine can not first connect the vm use ssh in that case.
docker-machine core implementation is create id_rsa, id_rsa, *.pem based on $HOME/.docker/machine/certs/* before launch any vm.

And, docker also docker-machine is doing a secure remote connection use *.pem.

So, need to copy the locally created userdata.tar in the first.

zchee · 2015-11-21T22:17:31Z

@johanneswuerbach
But, not accurate, I will check by gdb from now.

johanneswuerbach · 2015-11-21T23:58:43Z

Looks like b2d is just dd-ing a tar on that specific partition containing the certs: https://github.com/boot2docker/boot2docker/blob/master/rootfs/rootfs/etc/rc.d/automount#L22

Maybe the xhyve driver could create the same using hdiutil and dd.

zchee · 2015-11-22T00:21:49Z

@johanneswuerbach I remembered.

Yes. The method was previously used.

docker-machine boot2docker provisioner requires ssh login to some of the setting.
e.g. https://github.com/docker/machine/blob/master/libmachine/provision/boot2docker.go#L117-L127

If not exist /var/lib/boot2docker/userdata.tar, boot2dokcer is automatically formatted own disk, and create *.pem.
and, did not write hostid_rsa.pub data into authorized_keys.
In that case, It means for ssh login is needs tcuser password.

create blank disk image use dd
    |
boot2docker automatically create some files
    |
ssh login use tcuser password
    |
delete *.pem, and copy the local pem to img. and edit authorized_keys

I knew this way, but I feel it's pushy.

Hmm...
Let me think about it.

johanneswuerbach · 2015-11-22T16:58:33Z

Works like a charm now! :-)

zchee · 2015-11-22T17:01:10Z

@johanneswuerbach Oh! Thanks :)

aybabtme · 2016-01-12T16:38:00Z

I've been trying for a while to get this working, but it fails to find the -F flag (introduced in an unmerged PR against xhyve):

$ docker-machine -D create -d xhyve xhyve-dev
...
(xhyve-dev) DBG | operation not supported by device
(xhyve-dev) DBG | xhyve: illegal option -- F
(xhyve-dev) DBG | Usage: xhyve [-behuwxMACHPWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]
(xhyve-dev) DBG |              [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] -f <fw>
...

The full output: debug.txt

zchee · 2016-01-12T16:43:18Z

@aybabtme Thanks issue :)

Could you create a new issue thread?

aybabtme · 2016-01-12T16:45:12Z

@zchee cool, just opened #59

rothomp3 · 2016-01-15T20:21:12Z

It's working for me! Only thing was for some reason it didn't set up the boot script for the XHYVE_EXPERIMENTAL_NFS_SHARE, so I had to manually ssh in and mount the NFS share. After doing that, it's cranking away on building Swift from source now!

zchee · 2016-01-15T20:51:47Z

@rothomp3 Thanks a report!!

and, Sure thing for nfs issue.
I will create a issue threads, and debugging after fix already exists some of the issue :)
Could you provide us with information in order to solve the problem?

Jaesin · 2016-01-15T21:26:14Z

(xhyve-dev) DBG | Not there yet 1/60, error: IP not found for MAC 4a:db:63:46:cf:32 in DHCP leases
(xhyve-dev) DBG | operation not supported by device
(xhyve-dev) Waiting on a pseudo-terminal to be ready... virtio_net: Could not create vmnet interface, permission denied or no entitlement?
(xhyve-dev) DBG | exit status 1 &{0xc8200140f0} &{0xc820014120}
...
(xhyve-dev) DBG | Not there yet 60/60, error: IP not found for MAC 4a:db:63:46:cf:32 in DHCP leases
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting

zchee · 2016-01-15T21:29:06Z

@Jaesin Hi,

Could you try this command and post result?

ls -la $(which -a docker-machine-driver-xhyve)

Jaesin · 2016-01-15T21:34:50Z

I just wiped it out and started again and got it to work. 3rd try is a charm!

Thanks for the effort @zchee

docker-machine ssh xhyve-dev
(xhyve-dev) Getting to VM state...
                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/
 _                 _   ____     _            _
| |__   ___   ___ | |_|___ \ __| | ___   ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__|   <  __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
Boot2Docker version 1.9.1, build master : cef800b - Fri Nov 20 19:33:59 UTC 2015
Docker version 1.9.1, build a34a1d5
docker@boot2docker:~$

zchee · 2016-01-15T21:36:12Z

@Jaesin 🎉

far-blue · 2016-01-16T10:03:57Z

Didn't use the NFS flag as I already have some NFS stuff setup.

Worked brilliantly with Boot2Docker - b2d image 1.9.1

Didn't work with RancherOS because the ROS image has a vmlinuz file, not a vmlinuz64 file - ROS image 0.4.2

When it failed with ROS, it didn't clean up after itself (left the mount point).
Within B2D it was reporting it had 17GiB ram when running top .

zchee · 2016-01-16T10:14:16Z

@far-blue Thanks, issue :) and reporting.
but, I am not good English :(
So, I do not yet understand all.

Do you want to run the RancherOS use docker-machine-driver-xhyve?

Within B2D it was reporting it had 17GiB ram when running top.

ram...? In fact, that means available B2D memory size?

jawher · 2016-01-16T11:24:48Z

I just installed and tested xhyve-docker-machine-driver on OS X El Capitan, docker machine 0.5.6, and it worked brilliantly from the first try with a fairly complex project involving:

running 3 containers (1 mongodb, 1 api server and 1 web app on nginx)
using a bridge network
mounting host files and directories using the experimental nfs share
mounting the docker socket as a volume in the server container
building docker images inside the server container
and running the generated image

So big thanks to @zchee (and the xhyve project too) and keep up the good work !

far-blue · 2016-01-16T12:38:04Z

@zchee:

Do you want to run the RancherOS use docker-machine-driver-xhyve?

Yes, RancherOS (https://github.com/rancher/os) has support for docker-machine as an alternative for Boot2Docker and it provided support for xhyve early on. This is the command I used:

docker-machine create --driver xhyve --xhyve-boot2docker-url https://github.com/rancher/os/releases/download/v0.4.2/rancheros.iso dev

ram...? In fact, that means available B2D memory size?

When I ssh into boot2docker (docker-machine ssh dev) and run top I receive the following:

Tasks:  93 total,   1 running,  92 sleeping,   0 stopped,   0 zombie
%Cpu0  :   0.7/0.0     1
GiB Mem : 17.2/0.973
GiB Swap:  0.0/0.207

This might be something best reported to the xhyve project but I just wanted to mention it :)

zchee · 2016-01-16T12:52:05Z

@far-blue I understand :)

RancherOS provision does not support Now. Currently, boot2docker only :(
but, I was planning to support CoreOS and RancherOS provisioning from previous.

However, The first goal is to work perfectly the boot2docker.
I think boot2docker is a standard specification of use the docker in OSX.
What do you think?

BTW, If the PR does not come, I want to start with its implementation in about next month.

zchee · 2016-01-16T12:55:54Z

@jawher Thanks for Detailed reporting of operations!!
This report is good references to me.

I’m going to give it everything I’ve got.

far-blue · 2016-01-16T13:01:31Z

@zchee:

RancherOS provision does not support Now. Currently, boot2docker only :(

Given RancherOS has worked with xhyve in the past (rancher/os#379) my guess is that you just need to modify the following line to check for either 'vmlinuz64' or 'vmlinuz':

https://github.com/zchee/docker-machine-driver-xhyve/blob/d61209a16e2082074a146da646d3e7269da94ab9/xhyve/xhyve.go#L710

However, you are right, it is best to focus on Boot2Docker first because it is the default and most widely used configuration :)

And thank you for all the work you've done so far - it is looking great!

dwijnand · 2016-01-18T17:46:23Z

I followed the guide in https://allysonjulian.com/setting-up-docker-with-xhyve/ and it worked like a charm.

However when I then started setting up a project to use vagrant, with docker as the provider, it wanted to download the virtualbox box as a host rather than my local dev docker machine.

I've limited experience so I'd love a pointer in the right direction.

Thanks for the project.

lenn4rd · 2016-01-20T19:34:39Z

Great that you created this driver, thanks! 🙌🏼 I wanted to use xhyve in a Docker context for some time but didn't find the time to get familiar with the tooling and automation.

I installed docker, docker-machine, xhyve and docker-machine-driver-xhyve using Homebrew. Running the following doesn't succeed:

$ docker-machine create xhyve-vm -d xhyve
Running pre-create checks...
Creating machine...
(xhyve-vm) Copying /Users/lenn4rd/.docker/machine/cache/boot2docker.iso to /Users/lenn4rd/.docker/machine/machines/xhyve-vm/boot2docker.iso...
(xhyve-vm) Creating VM...
(xhyve-vm) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(xhyve-vm) /dev/disk5                                           /Users/lenn4rd/.docker/machine/machines/xhyve-vm/b2d-image
(xhyve-vm) "disk5" unmounted.
(xhyve-vm) "disk5" ejected.
(xhyve-vm) Generating 20000MB disk image...
(xhyve-vm) created: /Users/lenn4rd/.docker/machine/machines/xhyve-vm/root-volume.sparsebundle
(xhyve-vm) Creating SSH key...
(xhyve-vm) Fix file permission...
(xhyve-vm) Generate UUID...
(xhyve-vm) Convert UUID to MAC address...
Error creating machine: Error in driver during machine creation: exit status 1

I remember that xhyve has or had some issues creating network interfaces unless it is executed as root, so I tried sudo:

# sudo docker-machine create xhyve-vm -d xhyve
Password:
Running pre-create checks...
Creating machine...
(xhyve-vm) Copying /Users/lenn4rd/.docker/machine/cache/boot2docker.iso to /Users/lenn4rd/.docker/machine/machines/xhyve-vm/boot2docker.iso...
(xhyve-vm) Creating VM...
(xhyve-vm) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(xhyve-vm) /dev/disk6                                           /Users/lenn4rd/.docker/machine/machines/xhyve-vm/b2d-image
(xhyve-vm) "disk6" unmounted.
(xhyve-vm) "disk6" ejected.
(xhyve-vm) Generating 20000MB disk image...
(xhyve-vm) created: /Users/lenn4rd/.docker/machine/machines/xhyve-vm/root-volume.sparsebundle
(xhyve-vm) Creating SSH key...
(xhyve-vm) Fix file permission...
(xhyve-vm) Generate UUID...
(xhyve-vm) Convert UUID to MAC address...
(xhyve-vm) Starting xhyve-vm...
(xhyve-vm) Waiting for VM to come online...
(xhyve-vm) Waiting on a pseudo-terminal to be ready... done
(xhyve-vm) Hook up your terminal emulator to /dev/ttys004 in order to connect to your VM
Waiting for machine to be running, this may take a few minutes...
(xhyve-vm) Getting to VM state...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect Docker to this machine, run: docker-machine env xhyve-vm

I had to try a couple of times to chown the entire VM, enable it unsuccessfully, remove it and re-create it and on the third try I'm able to use it:

$ eval $(docker-machine env xhyve-vm)
$ docker-machine ls
NAME       ACTIVE   URL            STATE     URL                       SWARM   DOCKER    ERRORS
xhyve-vm   *        xhyve          Running   tcp://192.168.64.4:2376           v1.9.1

I was able to do a quick test as per @dwijnand's blog post.

Is there an easier way not using sudo? Or am I missing a step? I remember reading about code-signing the xhyve binary to be able to use it without sudo but I haven't tried this yet.

prologic · 2016-06-06T05:45:07Z

I can confirm success as well. Created the machine; Ran a test image.

aaronjensen · 2016-07-03T19:06:00Z

Works great for me with dinghy.

velikanov · 2016-07-05T14:56:05Z

OK @ home
NOT OK with XHYVE_EXPERIMENTAL_NFS_SHARE @ work

Strech · 2016-07-06T13:26:25Z

Wanna say HUGE thanks to @zchee ! We have 10+ successful installations on the various versions of OSX, from 10.10.5 to 10.11.4. All setups are working fine with NFS options.

Thanks! ❤️

cmoulliard · 2016-07-15T08:07:03Z

Doesn't work for me using docker-machine 0.7 & this MacOS version

ProductName:    Mac OS X
ProductVersion: 10.11.5
BuildVersion:   15F34

Error

docker-machine -D create --driver xhyve dev-xhyve
Docker Machine Version:  0.7.0, build a650a40
Found binary path at /usr/local/bin/docker-machine-driver-xhyve
Launching plugin server for driver xhyve
Plugin server listening at address 127.0.0.1:60681
() DBG | operation not supported by device
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at /usr/local/bin/docker-machine-driver-xhyve
Launching plugin server for driver xhyve
Plugin server listening at address 127.0.0.1:60685
() DBG | operation not supported by device
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(dev-xhyve) Calling .GetMachineName
(dev-xhyve) Calling .DriverName
(dev-xhyve) Calling .GetCreateFlags
(dev-xhyve) Calling .SetConfigFromFlags
Running pre-create checks...
(dev-xhyve) Calling .PreCreateCheck
(dev-xhyve) DBG | ===== Docker Machine xhyve Driver Version 0.2.2 (Homebrew) =====
(dev-xhyve) DBG |
(dev-xhyve) DBG | executing: /usr/local/bin/VBoxManage -v
(dev-xhyve) DBG | STDOUT: 5.0.20r106931
(dev-xhyve) DBG |
(dev-xhyve) DBG | STDERR:
(dev-xhyve) Calling .GetConfigRaw
Creating machine...
(dev-xhyve) Calling .Create
(dev-xhyve) DBG | local Boot2Docker ISO version:  v1.11.2
(dev-xhyve) Copying /Users/chmoulli/.docker/machine/cache/boot2docker.iso to /Users/chmoulli/.docker/machine/machines/dev-xhyve/boot2docker.iso...
(dev-xhyve) Creating VM...
(dev-xhyve) DBG | Mounting boot2docker.iso
(dev-xhyve) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(dev-xhyve) DBG | executing: &{/usr/bin/hdiutil [hdiutil attach /Users/chmoulli/.docker/machine/machines/dev-xhyve/boot2docker.iso -mountpoint /Users/chmoulli/.docker/machine/machines/dev-xhyve/b2d-image] []  <nil> 0xc82008a008 0xc82008a010 [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>} attach /Users/chmoulli/.docker/machine/machines/dev-xhyve/boot2docker.iso -mountpoint /Users/chmoulli/.docker/machine/machines/dev-xhyve/b2d-image
(dev-xhyve) DBG | hdiutil: attach failed - Operation timed out
Error creating machine: Error in driver during machine creation: exit status 1
Opting out of crash reporting.

jvz · 2016-07-25T19:50:35Z

Works fine for me. Installed from homebrew (version 0.2.2), created a new docker-machine using the xhyve driver, tried out some images, everything seems to work fine. Mac OS X 10.11.5.

firegate666 · 2016-08-12T16:41:28Z

Before I was using docker quickstart for mac with virtualbox and recently switched to dinghy with xhyve provider. I have installed your plugin using homebrew. Everything worked out of the box. No problems with our old images, no problems with new images.

Thanks a lot!

alexellis · 2016-08-12T16:46:45Z

I still can't get the xhyve driver to work. Unless people need multiple VMs I'd suggest using Docker for Mac which is in 1.12 GA now and the previous closed Beta is now open to anyone with a Stable and Beta channel:

https://docs.docker.com/docker-for-mac/

sylvek · 2016-08-12T16:52:08Z

Works properly with homebrew.. Thks!

Le ven. 12 août 2016 18:46, Alex Ellis [email protected] a écrit :

I still can't get the xhyve driver to work. Unless people need multiple
VMs I'd suggest using Docker for Mac which is in 1.12 GA now.
https://docs.docker.com/docker-for-mac/

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#18 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACJ4nbplnUPMbdvxX3l-9OYQQzrhOOjSks5qfKN4gaJpZM4Gm-ax
.

keplersj · 2016-08-13T05:13:07Z

Works awesome! Using TensorFlow in a Docker container, with modified CPU shares and shared folders, right now.

damienstanton · 2016-08-25T15:23:00Z

It works just fine following the homebrew installation and permissions instructions. 👍
Testing from macOS 10.11.6

feffi · 2016-08-28T19:44:03Z

Works like a charm:

docker, 1.12.1, Poured from bottle on 2016-08-28 at 21:06:28
docker-machine, 0.8.1, Poured from bottle on 2016-08-28 at 21:06:48
xhyve, HEAD, Built from source on 2016-08-28 at 20:49:03
docker-machine-driver-xhyve, 0.2.3, Poured from bottle on 2016-08-28 at 21:10:35

brew install docker docker-machine xhyve docker-machine-driver-xhyve
sudo chown root:wheel $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
docker-machine create default --driver xhyve --xhyve-experimental-nfs-share

Creating CA: /Users/****/.docker/machine/certs/ca.pem
Creating client certificate: /Users/****/.docker/machine/certs/cert.pem
Running pre-create checks...
Creating machine...
(default) Image cache directory does not exist, creating it at /Users/****/.docker/machine/cache...
(default) No default Boot2Docker ISO found locally, downloading the latest release...
(default) Latest release for github.com/boot2docker/boot2docker is v1.12.1
(default) Downloading /Users/****/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.12.1/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(default) Copying /Users/****/.docker/machine/cache/boot2docker.iso to /Users/****/.docker/machine/machines/default/boot2docker.iso...
(default) Creating VM...
(default) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(default) /dev/disk2                                            /Users/****/.docker/machine/machines/default/b2d-image
(default) "disk2" unmounted.
(default) "disk2" ejected.
(default) Generating 20000MB disk image...
(default) created: /Users/****/.docker/machine/machines/default/root-volume.sparsebundle
(default) Creating SSH key...
(default) Fix file permission...
(default) Generate UUID...
(default) Convert UUID to MAC address...
(default) Starting default...
(default) Waiting for VM to come online...
(default) Waiting on a pseudo-terminal to be ready... done
(default) Hook up your terminal emulator to /dev/ttys001 in order to connect to your VM
(default) NFS share folder must be root. Please insert root password.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!

    Hardware Overview:
      Model Name: MacBook Pro
      Model Identifier: MacBookPro11,3
      Processor Name: Intel Core i7
      Processor Speed: 2,8 GHz
      Number of Processors: 1
      Total Number of Cores: 4
      L2 Cache (per Core): 256 KB
      L3 Cache: 6 MB
      Memory: 16 GB
      Boot ROM Version: MBP112.0138.B17
      SMC Version (system): 2.19f12
      Serial Number (system): <serial>
      Hardware UUID: <put-some-unique-id-here>

johanngeir · 2016-08-30T00:05:07Z

Everything worked after installing with Homebrew, except Docker wasn't able to pull images because of a DNS problem. It turns out that my dnsmasq server running on localhost was conflicting with xhyve driver's local DNS server running on 192.168.64.1

After uninstalling my dnsmasq server, I recreated the xhyve machines and then they worked (in hindsight, it might have been sufficient to just restart them).

Now everything seems to work.

Hope it helps.

Morendil · 2016-09-22T09:15:08Z

Seems to work mostly fine. First creation failed with "virtio_net: Could not create vmnet interface, permission denied or no entitlement?" - I deleted and tried again, and the second time it did work.

bglusman · 2016-09-29T02:46:05Z

Working for me.

bglusman · 2016-10-05T21:08:53Z

Actually, initially worked, but seemed problematic on minikube across restarts/machine restarts so I went back to virtualbox... not definitive, but FYI

r2d4 · 2016-10-05T21:16:55Z

@bglusman can you tell us what went wrong? Feel free to open an issue on minikube too if you think its appropriate. Thanks :)

coodoo · 2016-10-10T06:26:12Z

Worked like a charm on 10.11.6, good job!

tclarke · 2016-10-25T14:40:31Z

Working well on 10.12 with virtio-9p. Running fairly complicated docker-compose development setups (with volume mounts to local source, etc.)

alexei-led · 2016-12-18T16:36:55Z

Works well with following versions

docker-machine version 0.9.0-rc2, build 7b19591
docker client 1.13.0-rc3
MAcOS: v10.12.3, build 16D12b

HerrmannHinz · 2017-02-24T13:01:10Z

works for me:

docker-machine: docker-machine version 0.9.0, build 15fd4c7
docker: Docker version 1.13.1, build 092cba3
osx: Mac OS X - 10.12.4 - 16E154a
docker-machine-driver-xhyve: 0.3.1

gpyzy · 2017-08-24T00:17:42Z

Not sure if there is still a need to post here but the driver successfully works on my mac with the beta docker 7.07.0-ce-rc3-mac23 (18949) and RancherOS VM!

docker-machine version 0.12.2, build 9371605
osx version macOS Sierra 10.12.6

momo182 · 2017-10-29T10:44:07Z

installed via brew install xhyve docker-machine-driver-xhyve, works like a charm!

System Version: macOS 10.13 (17A405)

iBobik · 2018-05-14T17:42:05Z

Works.

macOS 10.13.4 (17E202)

schuster-rainer · 2018-07-13T14:18:58Z

I have a couple of hours on an investigation to report ... It all started with using Volumes. So after checking the known issues and seeing #90 and a lot more research finally I figured out the issue, but not the root cause yet.

My external drive is a Samsung T3 with NTFS .. I guess thats the issue, because every file gets a 777 permission. So fixing permissions on creation doesn't work. Took me a while to get and figure out permissions aren't set correctly.

Maybe this helps for other users trying to solve the issue with external volumes

vishworks · 2019-01-10T09:00:15Z

Fails on macOS 10.14.2
Tried building from source.
Breaks with the following error when attempting to start minishift (after building from source - 0.3.3.1)
json: cannot unmarshal bool into Go struct field Driver.Virtio9p of type []string

mavimo · 2019-03-02T16:36:08Z

@vishworks same issue here, I fixed by editing ~/.minikube/machines/minikube/config.json by replacing:

        "Virtio9p": true,
        "Virtio9pFolder": "/Users",

with:

        "Virtio9p": [
            "/Users"
        ],
        "Virtio9pRoot": "/",

praveenkumar · 2019-03-02T17:51:56Z

@vishworks it is also tracked on minishift side minishift/minishift#3180 (comment)

mroi · 2019-11-13T12:09:03Z

Works beautifully for me. Installed using Nix.
macOS 10.15.2 Beta (19C32e)

em0t · 2020-08-07T11:38:08Z

Not works well with me

macOs Catalina 10.15.6
Docker version 19.03.12, build 48a66213fe
Docker Machine Version:  0.16.2, build bd45ab1
docker-machine-driver-xhyve: stable 0.4.0 (bottled), HEAD

I have run grant policy command:

 sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
 sudo chmod u+s /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve

But when i execute create command, i get UUID error:

~ docker-machine create --driver xhyve worker1
...
(worker1) Convert UUID to MAC address...
Error creating machine: Error in driver during machine creation: Could not convert the UUID to MAC address: exit status 1

I'm searching around the google, but not help me

I have open an issue #230

zchee changed the title ~~Reporting for launched vm~~ Reporting for launched xhyve Nov 21, 2015

johanneswuerbach mentioned this issue Nov 22, 2015

Generate disk image using hdiutil #19

Merged

zchee mentioned this issue Jan 15, 2016

Didn't set up the boot script for the XHYVE_EXPERIMENTAL_NFS_SHARE #71

Open

Reporting for launched xhyve #18

Reporting for launched xhyve #18

Comments

zchee commented Nov 21, 2015

johanneswuerbach commented Nov 21, 2015

zchee commented Nov 21, 2015

johanneswuerbach commented Nov 21, 2015

zchee commented Nov 21, 2015

zchee commented Nov 21, 2015

johanneswuerbach commented Nov 21, 2015

zchee commented Nov 22, 2015

johanneswuerbach commented Nov 22, 2015

zchee commented Nov 22, 2015

aybabtme commented Jan 12, 2016

zchee commented Jan 12, 2016

aybabtme commented Jan 12, 2016

rothomp3 commented Jan 15, 2016

zchee commented Jan 15, 2016

Jaesin commented Jan 15, 2016

zchee commented Jan 15, 2016

Jaesin commented Jan 15, 2016

zchee commented Jan 15, 2016

far-blue commented Jan 16, 2016

zchee commented Jan 16, 2016

jawher commented Jan 16, 2016

far-blue commented Jan 16, 2016

zchee commented Jan 16, 2016

zchee commented Jan 16, 2016

far-blue commented Jan 16, 2016

dwijnand commented Jan 18, 2016

lenn4rd commented Jan 20, 2016

prologic commented Jun 6, 2016

aaronjensen commented Jul 3, 2016

velikanov commented Jul 5, 2016

Strech commented Jul 6, 2016

cmoulliard commented Jul 15, 2016

jvz commented Jul 25, 2016 • edited Loading

firegate666 commented Aug 12, 2016

alexellis commented Aug 12, 2016 • edited Loading

sylvek commented Aug 12, 2016

keplersj commented Aug 13, 2016

damienstanton commented Aug 25, 2016

feffi commented Aug 28, 2016

johanngeir commented Aug 30, 2016 • edited Loading

Morendil commented Sep 22, 2016

bglusman commented Sep 29, 2016

bglusman commented Oct 5, 2016

r2d4 commented Oct 5, 2016

coodoo commented Oct 10, 2016

tclarke commented Oct 25, 2016

alexei-led commented Dec 18, 2016

HerrmannHinz commented Feb 24, 2017

gpyzy commented Aug 24, 2017

momo182 commented Oct 29, 2017

iBobik commented May 14, 2018

schuster-rainer commented Jul 13, 2018

vishworks commented Jan 10, 2019

mavimo commented Mar 2, 2019

praveenkumar commented Mar 2, 2019

mroi commented Nov 13, 2019

em0t commented Aug 7, 2020 • edited Loading

jvz commented Jul 25, 2016 •

edited

Loading

alexellis commented Aug 12, 2016 •

edited

Loading

johanngeir commented Aug 30, 2016 •

edited

Loading

em0t commented Aug 7, 2020 •

edited

Loading