Rancher fails to pull system dockers in cloud-config.yml during boot

[bf8392]

RancherOS Version: (ros os version)
1.5.4

Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
Virtual Box

The VM Fails to connect after several boots and pull system dockers. Especially when alter the user-config.yml under /var/lib/rancher/conf/cloud-config.d I encounter problems. Is there a solution? Or is it not ment to be altered with vi? Is there another way to alter cloud-config?

[niusmallnan]

Can you show me more details? Your steps and cloud-config.

[bf8392]

Steps were:

1. Bootet rancheros
2. wrote cloud-config with vi
3. installed rancheros with the Ros install -c cloud-config -d commands
4. waitet for installation
5. Bootet and sshd in the new rancheros (everything works fluently till here. The config seems to be fully working [additional services are installed, SSH keys work, the partition is expanded etc.]
6. then I trie to alter the file in /var/lib/rancher/conf/cloud-config-d/user-config.yml with vi to add new settings to cloud config.
7. save file
8. validate file
9. when validation is ok (nothing is displayed) I reboot the machine
10. after reboot the console displays that it can't connect to the docker/index/v2.io because the network is unreachable

It doesn't matter when I change.the adapter for virtual box, its always the same. I can't regain connection to the new installation

[bf8392]

Here is my Cloud-Config:

#cloud-config

set ssh-key

ssh_authorized_keys:

• ssh-rsa AAAASOMEKEY123

set hostname

hostname: YourRancher

THE RANCHER KEY

rancher:

resize the device-partition

resize_device: /dev/sda

setup networking

network:
dns:
nameservers:
- 1.1.1.1
- 1.0.0.1

set system services

services_include:
kernel-headers-system-docker: true
kernel-headers: true
kernel-extras: true

setup custom system-services

services:
fail2ban:
image: crazymax/fail2ban
container_name: fail2ban
net: "host"
cap_add:
- NET_ADMIN
- NET_RAW
volumes:
- /custom_services_bd/fail2ban/data/:/data
- /custom_services_bd/fail2ban/log/:/var/log:ro
restart: always
labels:
io.rancher.os.scope: system
~
~

[bf8392]

After Booting, it pulls dockers without problem. Also SSH into the machine works. but during boot, no network seems available...it seems that rancher isn't waiting till the network is up after it booted first...also the ip adress is not displayed in console.

[bf8392]

I tried creating a new virtual machine several times and always run into the same issue - not network on boot to pull custom system services. When I put a script to wait on network before continuing boot, booting hangs and never gets further. The issue also occurs when I don't alter the config. On first boot, everything seems to work fine, but as soon as I reboot, the issue is there...

[bf8392]

Anyone? I tried everything and nothing helps =( please help! I love the approach of Rancher/OS and want to use it in all my server-environments...

[Jason-ZW]

@bd8392 I will give it a try. After that, I will give u feedback ASAP

[Jason-ZW]

Same problems. The first reboot no errors occur, but when changing the user_config.yml then reboot, the problem comes.

[bf8392]

Yes thank you. I also tried to configure the network like this:

rancher:

resize the device-partition

resize_device: /dev/sda

setup networking

network:
interfaces:
eth*:
dhcp: true
mtu: 1500
dns:
nameservers:
- 1.1.1.1
- 1.0.0.1
doesn't help either...tried everything now...the wait for the network workaround described in #2653 (comment)
leads to boot-halt. Rancheros reports started, but nothing happens anymore and you can't acces anything when implementing this code...

[bf8392]

Any news on this? still had no luck trying to configure...