-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Rancher Server #21
Comments
Thank you for reporting those issues, We will wait a little bit for an answer from the @rancher team on their issue |
Taring with only the go static binary at the root (no folder) did the trick! |
Ok cool, I just added another upload here: https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.0.2/docker-machine-driver-scaleway.tar.gz, you should be able to use the url directly in rancher |
Oups, I gave you the bad link in the other issue, can you try with this link : https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.0.2/docker-machine-driver-scaleway.tar.gz (a tarball with only the go binary without folder) |
@moul that url is not working neither 1.2 relase |
@jalberto, yep I only succeed by putting the binary without tarball, we will probably release the binary for linux x86_64 then @QuentinPerez, can you upload the binary please ? |
It works for me wit a zip file containing only the binary On Tue, 10 May 2016 07:58 Manfred Touron, [email protected] wrote:
|
@moul @QuentinPerez @jalberto ok same issue for me, it only works within a zip (nor tgz) file... :( Rancher also released as skel project for custom machine drivers: Would be cool to provide some skel for scaleway ;) |
@jalberto don't work when zipping it. Which version of rancher do you use? (I'm using 1.0.1 ATM). |
It did work for me on 1.1.0 inside the zip file you only need the binary Anyway this driver is yet quite limited, I found faster just to use scaleway UI |
@jalberto ok thx I will try with 1.1.0 ;) I already use the driver with docker-machine & it fits all my needs. I will just provide a skel following https://github.com/rancher/ui-driver-skel spec. |
great :) On Thu, 19 May 2016 at 12:19 Sébastien HOUZÉ [email protected]
|
@pascalandy yes, I will stuck with docker stuff only till rancher-compose support docker-compose v2 format rancher/rancher#3973 (because libcompose itself still not ready for v2 format docker/libcompose#147). |
Hi, |
@clescot yes that's great but volumes & networks have some issues opened rancher/rancher#5714 & rancher/rancher#5715. BTW, close to the goal ;) |
Hi, just wanted to know if this is working? and if so what URL are you using in rancher to download the machine driver? thanks! EDIT: got it to install using the latest tar.gz, for some reason it didnt work at first...anyways, if anyone has developed a skel it would be cool to share :) |
@RVN-BR If I'm following you correctly you have managed to get Rancher OS v0.6.1 running on a Scaleway instance? That's great if so. I've been trying to build a custom Rancher OS image for use on Scaleway VC1 or C2's with this: I already have Rancher hosts running off Ubuntu derived images on Scaleway, but I'm keen to use Rancher OS as the base image for my hosts instead. I'm hoping that it'll use a lot less memory than the Scaleway default Docker image. I did try this: https://github.com/rancher/os-installer But I've had no luck and just get a kernel panic on boot, think this is because Scaleway ignores vmlinuz and initrd and uses it's own instead. If you have managed to get Rancher OS working on Scaleway would you be willing to share the steps required and perhaps and example of your docker-machine line? Thanks :-) |
Hi @robeastham in fact I didnt get that far :( I actually wasnt even able to get the docker-machine driver working... (although I think its a question of looking at the scaleway API and filling in the options correctly). I'll probably look into this a bit later as I havent had a lot of time... I was going to have it start an ubuntu image, at least initially... hadnt thought of giving rancher os another try... I had some troubles with it and then ended up not using it anymore... Have you been using ROS in production? thanks! |
@RVN-BR no not using in production yet. But hope to soon with my setup. I have a Rancher Server running on an EC2 instance, that is running Rancher OS. But I plan to use Scaleway as much as possible for hosts as they are much better value when compared to EC2 instances. I've just settled with the default Ubuntu based Docker image for now for my hosts on scaleway. VC1L seem like the best value. So my Rancher Hosts on Scaleway just work with my EC2 Rancher Server when I pick this image. I tried the Scaleway Alpine images too, but had problems with K8S containers communicating and starting despite picking the Docker boot scripts. It would be great to get Rancher OS as an official OS image supported by Scaleway as I think it will cut down on the memory requirements for hosts. Perhaps @moul could comment on whether we are likely to see this? I think Scaleway would sell more instance hours if they supported Rancher OS out of the gate. It wouldn't take long for word to get around the Rancher community and for others running Docker containers. |
Got it @robeastham ... I am having a bit of trouble with getting hosts to connect to a rancher server on a scaleway instance... I need to create a different set of security group rules I think.... I tried using the internal scaleway IP (rancher agent and rancher server on scaleway) but it didnt work... I keep getting http://10.x.x.x:8080/v1 is inaccessible errors on the rancher log... (ping works, etc), anyways, thats a diferent issue... I wanted to use Rancher on scaleway mostly for test loads, unfortunately most of our traffic is in South America and the lag to Scaleway is significant... But for testing loads I find the scaleway pricing pretty fantastic 👍 I'm going to give RancherOS another spin soon... I havent really touched it in a while... I think a rrancheros image would indeed help a lot for european customers at least... And the Rancher Community seems pretty active so I guess unless its something very difficult it would be wise for them... CoreOS is also notably not on their list... Previously I was tesing mostly on coreos...will have to give ros another shot. |
Two questions here:
http://docs.rancher.com/rancher/v1.2/en/configuration/machine-drivers/ |
For rancher 1.2 I've used There's no ui for that (not sure whether the new ui is working) For rancher 1.6 there's also a working ui: ui url: |
Well just a follow up not in terms of RancherOS but general use of Rancher. I am running a simple Rancher cluster as we speak out of VC1S machines with docker instances. Then I added via a custom machine driver a node and it is working as a charm, even though that the Rancher UI says incompatible!!! |
Continuing previous comments, |
I've submitted an issue on the rancher issue track as the release doesn't install: rancher/rancher#4486
Not sure if this driver has something to do with it. I was able to install the Vultr one.
The text was updated successfully, but these errors were encountered: