I've run into a few situations where the server somehow gets a new IP after reboot and I had to discover IP through arp and DHCP server.

A console login would be handy, especially for bare metal installs.

Example of running poweroff as user on ubuntu

$ poweroff
poweroff: Need to be root

I did not look deep into it, but it seems to be missing some network drivers/device.

No reboot should be required.

The networking does not initialize lo with 127.0.0.1 in the host namespace. For a temporary work around just run

sudo system-docker --net=host --privileged debian ip addr add 127.0.0.1/8 dev lo

In the latest 0.0.3 release, if I run poweroff as rancher user, I get a go panic.

sudo poweroff works

Try to connect to any local IP, say the one on the eth0 interface. That'll take forever, so you just can't.

From my terminal:

rancher@rancher:~$ ip addr show dev eth0

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:22:20:2e brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe22:202e/64 scope link 
       valid_lft forever preferred_lft forever


rancher@rancher:~$ ping 10.0.2.15

PING 10.0.2.15 (10.0.2.15) 56(84) bytes of data.
^C
--- 10.0.2.15 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4004ms

Why???

                          df: /sys/fs/cgroup/devices: No such file or directory
                          df: /sys/fs/cgroup/freezer: No such file or directory
                          df: /sys/fs/cgroup/memory: No such file or directory
                          df: /sys/fs/cgroup/net_cls: No such file or directory
                          df: /sys/fs/cgroup/perf_event: No such file or directory
                          /dev/vda              20511356    141116  19305280   1% /var
                          none                    512268         8    512260   0% /var/run
                          df: /var/lib/docker/overlay/80811ffbdb54d378f701f17dadfd33d097e4c2553ca5e3b97d4e
                          1bece7a97b10/merged: No such file or directory
                          df: /var/lib/docker/overlay/73a32b21e82d40f9b2ab2bb2fb116805396ed9f57449999290da
                          8aa74fbf4704/merged: No such file or directory
                          df: /var/lib/docker/overlay/26446ede5979e952e218673f945d67c5550712e3f93ce2032978
                          750e940e32e5/merged: No such file or directory
                          overlay               20511356    141116  19305280   1% /
                          tmpfs                   512268         0    512268   0% /dev
                          shm                      65536         0     65536   0% /dev/shm
                          /dev/vda              20511356    141116  19305280   1% /etc/resolv.conf
                          /dev/vda              20511356    141116  19305280   1% /etc/hostname
                          /dev/vda              20511356    141116  19305280   1% /etc/hosts
                          /dev/vda              20511356    141116  19305280   1% /home
                          /dev/vda              20511356    141116  19305280   1% /opt
                          /dev/vda              20511356    141116  19305280   1% /var/lib/rancher/conf
                          none                    512268         8    512260   0% /var/run

There seems to be a bug in busybox top command:

Mem: 449532K used, 159356K free, 0K shrd, 0K buff, 139914323006485K cached
CPU: 0% usr 0% sys 0% nic 99% idle 0% io 0% irq 0% sirq
Load average: 0.00 0.01 0.05 1/111 598
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
1 0 root S 700m 118% 0% docker -d -s overlay -b none --restart
208 1 root S 485m 81% 0% docker -d -s overlay --tlsverify --tls
267 1 root S 147m 25% 0% respawn -f /etc/respawn.conf
198 1 root S 54068 9% 0% rsyslogd -n
548 546 rancher S 20088 3% 0% sshd: rancher@pts/4
557 555 rancher S 20076 3% 0% sshd: rancher@pts/5
530 333 root S 20076 3% 0% sshd: rancher [priv]
496 494 rancher S 20076 3% 0% sshd: rancher@pts/0
546 333 root S 20076 3% 0% sshd: rancher [priv]
538 333 root S 20076 3% 0% sshd: rancher [priv]
494 333 root S 20076 3% 0% sshd: rancher [priv]
555 333 root S 20076 3% 0% sshd: rancher [priv]
522 333 root S 20076 3% 0% sshd: rancher [priv]
532 530 rancher S 20076 3% 0% sshd: rancher@pts/2
524 522 rancher S 20076 3% 0% sshd: rancher@pts/1
540 538 rancher S 20076 3% 0% sshd: rancher@pts/3
333 267 root S 17484 3% 0% /usr/sbin/sshd -D
549 548 rancher S 14884 2% 0% -bash
497 496 rancher S 14884 2% 0% -bash
558 557 rancher S 14880 2% 0% -bash

Booted the 0.0.3 iso under VMware Workstation. I have a 20G disk setup in VMware with default SCSI 0:0

first, the rancheros-install is not exist, i pull it from /scripts/dockerimages/scripts/rancheros-install
then, i use sudo rancheros-install -d /dev/sda -c ./cloud_data.yml -v v0.1.2 -t generic
it show me The file /dev/sda1 is not exist and no size was specified

When rebooting the SSH connections aren't closed. The client is left hanging until the timeout or you kill the ssh process.

It gets stuck at "Running [5/10] network"

Its something people do.

Vagrant runs:
shutdown -h now

when a user does a vagrant halt

Please publish EC2 compatible image in addtion to AMI.

Running the command ip addr show results in a segmentation fault. Running ifconfig works OK.

[rancher@rancher ~]$ ip addr show
1: lo: <LOOPBACK> mtu 65536 qdisc noop
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 08:00:27:fc:5f:eb brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
       valid_lft forever preferred_lft forever
Segmentation fault

SELinux and / or GRSecurity would greatly improve the potential for rancher to be used in production environments.

Looking at /var/log/userdocker.log you see

exec docker -d -s overlay --tlsverify --tlscacert=/etc/docker/tls/ca.pem --tlscert=/etc/docker/tls/server-cert.pem --tlskey=/etc/docker/tls/server-key.pem -H=0.0.0.0:2376 -H=unix:///var/run/docker.sock -G docker
time="2015-02-24T23:41:36Z" level="info" msg="+job serveapi(tcp://0.0.0.0:2376, unix:///var/run/docker.sock)" 
time="2015-02-24T23:41:36Z" level="fatal" msg="Couldn't create Tag store: unexpected end of JSON input" 

Perhaps we need to create a system container for running the Azure python agent?

I can't seem to find details on what file system is being used by default. Apologies if I did not look hard enough.

qemu-system-x86_64 -enable-kvm -cdrom rancheros.iso gives:

Kernel panic - not syncing: Unable to mount rootfs on unknown block(2,0)

This is with the latest ISOs, including the released and unreleased ones.

Hi, it seems that there are only AMI in US zones.
Could you add some for the european and APAC zones ?
thanks

It started just fine. I can also get on to the network and see /dev/sda. I was able to format the /dev/sda partition and give it the RANCHER_STATE label.

The problem is it fails to detect RANCHER_STATE partition after reboot.

Given a virtual machine with the following stats:

4 VCPUs
8 GB RAM
80 GB HDD

Running the latest rancheros.iso on qemu on openstack juno.

I expect that pulling a handful of images will succeed (assume the rancher-agent image already ran successfully). In my case, I tried running the dockerized version of gitlab with a few supporting containers.

Instead, the pull fails with 'no space remaining'. If I install docker on a trusty-taur vm of similar or smaller sizes, all steps above succeed with flying colors.

UPDATE:
Please used the packer repo here to build your own qemu image:
https://github.com/cloudnautique/rancher-packer

You should be able to create a flexible disk image and install cloud-init on it if you need that service too.

For those interested in an official Openstack build, see #261

User should be able to create new system services as containers within RancherOS.

It seems that if we pass some user-data to start a rancheros instance on EC2, a #cloud-config file will conflict with the keypair being used. Hence using the keypair to ssh into the instance fails.

I have not checked logs, but without specifying #cloud-config user data, ssh using the keypair works.

Rancher should be packaged together with RancherOS so that an install of RancherOS allows management of self and linked docker instances from boot

I'm already running 0.2.0-rc3, yet it still upgraded me to 0.2.0-rc3.

The system rebooted automatically after the upgrade. It should prompt me for reboot, at least put in a count down delay.

When I mistype the name of an addon it should have told me the addon does not exist:

[rancher@rancher ~]$ sudo rancherctl addon enable ubunut-console
[rancher@rancher ~]$ sudo rancherctl addon list
ubuntu-console disabled