RancherOS v1.0.1 - install process ignores the cloud-config.yml file


I created the cloud-config file under home/rancher.

hostname: rancherOS-test

    dhcp: false

  - ssh-rsa AAAAB3NzaC1yc2 . . . . /gOgVx62w== rancher-test

I tested the file with ros config validate…
(no output, so all is OK)

But after the install
Nothing is set in rancher.
No hostname

Where is my mistake.


@NITESupport what command did you use to do the install? How much memory does your VM have?


The VM (virtualbox - other linux 64bit)
it has 1024 MB memory
2 CPUs
2 network adapters
first - bridged
second - host-only

And the command i use is: (with tab completion)
sudo ros install -c cloud-config.yml -d /dev/sda


This is what i get when i start the installation
and i have a doubt about the Continue with reboot [y/N]:
when the cloud-config file is not copied to anywhere, so it’ll not be available after the reboot.

[rancher@rancher ~]$ sudo ros install -c cloud-config.yml -d /dev/sda
> INFO[0000] No install type specified...defaulting to generic
Installing from rancher/os:v1.0.1
Continue [y/N]: y
> INFO[0004] start !isoinstallerloaded
> INFO[0005] trying to load /bootiso/rancheros/installer.tar.gz
23b9c7b43573: Loading layer  4.23 MB/4.23 MB
f90562450ed7: Loading layer 14.96 MB/14.96 MB
94dbf06f5a27: Loading layer 4.608 kB/4.608 kB
52125c070e5e: Loading layer 18.08 MB/18.08 MB
051a95b6eaa9: Loading layer 1.636 MB/1.636 MB
a6fd95b21434: Loading layer 1.536 kB/1.536 kB
c52e27553689: Loading layer  2.56 kB/2.56 kB
7b425eeedf72: Loading layer 3.072 kB/3.072 kB
> INFO[0007] Loaded images from /bootiso/rancheros/installer.tar.gz
> INFO[0007] starting installer container for rancher/os-installer:latest (new)
Installing from rancher/os-installer:latest
mount: /dev/sr0 is write-protected, mounting read-only
Continue with reboot [y/N]:


I made a mistake.
I thought that the ISO is automatically ejected after the install.
So I was rebooting on the “live CD”. :disappointed_relieved:

So the machine boot and has all the configuration as expected, but,
I still have those errors during the boot

Ah yes, forgetting to eject the ISO has bit me before too. I haven’t seen those errors before (I’m just a user of RancherOS, not a dev), but I’ll ask around.

yeah - ISO ejection happens to all of us :confused:

I don’t really think those should be marked as errors anymore - especially on vbox.