# Unable to Create a RancherOS VM using docker-machine

**URL:** <https://forums.suse.com/t/unable-to-create-a-rancheros-vm-using-docker-machine/2714>\
**Category:** RancherOS\
**Created:** [May 7, 2016, 3:14am UTC](https://forums.suse.com/t/unable-to-create-a-rancheros-vm-using-docker-machine/2714 "2016-05-07T03:14:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Rush](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jeff_rush/32/3164_2.png) [@Jeff\_Rush](https://forums.suse.com/u/Jeff_Rush)\
**Post date:** [May 7, 2016, 3:14am UTC](https://forums.suse.com/t/unable-to-create-a-rancheros-vm-using-docker-machine/2714/1 "2016-05-07T03:14:33Z")

</div>

I tried to run it under VirtualBox using docker-machine  
and the instructions at:

```
http://rancher.com/getting-started-with-rancheros-2/

```

“You might notice that there are two .iso files, rancheros.iso  
and machine-rancheros.iso. machine-rancheros.iso is the file you  
want. This ISO has been built with special configuration for  
setup with docker-machine.”

but at the webpage of RancherOS ISO machines,

```
https://github.com/rancher/os/releases

```

there is not one prefixed with “machine-” to use with docker-machine.

The article was written about an older version of RancherOS, so thinking  
maybe that a separate machine-\* ISO image is no longer needed, I proceeded with the non-machone-\* ISO image.

But then I get:

```
 Error creating machine: Error checking the host: Error checking
 and/or regenerating the certs: There was an error validating
 certificates for host "192.168.100.100:2376":
 dial tcp 192.168.100.100:2376: getsockopt: connection refused

```

The exact same docker-create command works fine with boot2docker.iso.

Has RancherOS left behind usage with docker-machine? I’m just trying to  
get started and it’s been rough. I had to give up on bare-metal install onto  
vSphere for lack of doc about how to do that w/o DHCP network support,  
where you cannot just ‘ssh’ the key onto the new root drive.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [May 7, 2016, 3:54am UTC](https://forums.suse.com/t/unable-to-create-a-rancheros-vm-using-docker-machine/2714/2 "2016-05-07T03:54:10Z")

</div>

Did you look at the docs on how to launch RancherOS using docker-machine?

[http://docs.rancher.com/os/running-rancheros/workstation/docker-machine/](http://docs.rancher.com/os/running-rancheros/workstation/docker-machine/)

We removed the machine-rancheros.iso and the latest OS version (v0.4.4) supports launching with docker-machine.

---

<div class="post-metadata">

**Author:** ![Jeff\_Rush](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jeff_rush/32/3164_2.png) [@Jeff\_Rush](https://forums.suse.com/u/Jeff_Rush)\
**Post date:** [May 17, 2016, 9:46pm UTC](https://forums.suse.com/t/unable-to-create-a-rancheros-vm-using-docker-machine/2714/3 "2016-05-17T21:46:33Z")

</div>

I have carefully followed those instructions but important details are missing, such as specific software versions and the need to always remove failed hostonlyifs and docker-machines before trying again.

For example, I needed to upgrade my VirtualBox from 4.x to 5.x to make progress past my initial problem I reporte in this thread, because RancherOS ISO failed on the older version.

I still don’t have it working and here are my notes. I would apprecate any help as my company is evaluating RancherOS and Rancher for commercial adoption across our product line but so far, it isn’t looking good.

Versions:

```
  RancherOS v0.4.4 (latest stable)

  app-emulation/virtualbox-bin-5.0.20.106931:0
  app-emulation/virtualbox-modules-5.0.20:0

  app-emulation/docker-1.11.0:0 API version 1.23
  app-emulation/docker-machine-0.7.0:0 API version ?.??
  dev-python/docker-py-1.8.0_rc5:0 API version ?.??

  app-emulation/docker-compose-1.7.0:0
  dev-python/dockerpty-0.4.1:0

```

Steps:

1. Pre-clear any leftover host interfaces

2. Create the machine, without a hostonly interface

3. Puzzle: After the run there is an ISO file that I thought would be RancherOS but is tagged as Boot2Docker:

4. Try again, but specify the host-only cidr myself this time

5. Great, I now have a RancherOS machine!

6. But the Docker API in Docker and inside RancherOS are different, it seems:

7. Updating version of Docker inside RancherOS

I think the core problem now is how to use the latest version of docker client with the latest stable version of RancherOS when their APIs differ and there is no adaptive fallback or upgrade path forward.