# Create new host on Scaleway

**URL:** <https://forums.suse.com/t/create-new-host-on-scaleway/3872>\
**Category:** Rancher 1.x\
**Created:** [September 1, 2016, 10:38am UTC](https://forums.suse.com/t/create-new-host-on-scaleway/3872 "2016-09-01T10:38:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Hansen](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/thomas_hansen/32/1283_2.png) [@Thomas\_Hansen](https://forums.suse.com/u/Thomas_Hansen)\
**Post date:** [September 1, 2016, 10:38am UTC](https://forums.suse.com/t/create-new-host-on-scaleway/3872/1 "2016-09-01T10:38:45Z")

</div>

I am trying to use the scaleway docker-machine (v1.2.1) driver to create a new host from Rancher (1.1.3).

Using the same settings as I have successfully used from my linux workstation command line and docker-machine - I immediately get an error in Rancher: “exit status 1”.

I get the error so quickly that I doubt rancher has even tried to do anything on the rancher side.

Using View in API, I am not seeing any additional details that are of any use.

Has anyone else had this problem and managed to resolve it?

Is there somewhere I can find a more detailed log with the error?

---

<div class="post-metadata">

**Author:** ![Thomas\_Hansen](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/thomas_hansen/32/1283_2.png) [@Thomas\_Hansen](https://forums.suse.com/u/Thomas_Hansen)\
**Post date:** [September 1, 2016, 10:44am UTC](https://forums.suse.com/t/create-new-host-on-scaleway/3872/2 "2016-09-01T10:44:21Z")

</div>

I may have found it by running `docker logs`on the rancher server…

Looks like the command being created from rancher is the full name of the driver executable - “scaleway-linux-amd64” instead of “scaleway”.

This is also the name of the driver on the rancher machine driver overview.

Any know how I can change the name so that the command is created correctly? Do I need to tweak this on the host?

---

<div class="post-metadata">

**Author:** ![Thomas\_Hansen](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/thomas_hansen/32/1283_2.png) [@Thomas\_Hansen](https://forums.suse.com/u/Thomas_Hansen)\
**Post date:** [September 1, 2016, 10:50am UTC](https://forums.suse.com/t/create-new-host-on-scaleway/3872/3 "2016-09-01T10:50:10Z")

</div>

Funny how asking a question leads you to find the answers yourself 😉

Turns out I had installed the driver with a link to the uncompressed driver  
[https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.2.1/docker-machine-driver-scaleway-linux-amd64](https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.2.1/docker-machine-driver-scaleway-linux-amd64)

instead of

[https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.2.1/docker-machine-driver-scaleway\_1.2.1\_linux\_amd64.tar.gz](https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.2.1/docker-machine-driver-scaleway_1.2.1_linux_amd64.tar.gz)

Changing this to use the compressed driver seems to created a new driver on the rancher server with the correct name.