- Mar 26, 2016
hmm seems that its stuck on connected now, will see tomorrow how to fix it.
I followed this guide and it Works very well.Whats the current state of running RancherOS on FreeNAS 11 ? Is it functional?
Firstly, thanks to the OP the guide and everyone who has contributed to the thread.
I managed to get portainer up and running jumping back and forth through the pages. It would be a really great resource if the OP could be updated with the later improvements so everything was together?
Now just to work out what docker is all about and how I might use it :D
I should also mention I am using FreeNAS with a ssd cache drive on ZFS, I have read that the write sync can cause issues with NFS. I can also note that NZBGet downloads are incredibly slow when they used to be lightning fast in a FreeNAS Jail.
It's a free country. Bottom line is this guide is very dated since recent release(s) have incorporated docker via rancheros into the os and gui.
VM -> hit + -> fill out -> hit start
#/var/lib/rancher/conf/cloud-config.d/nfs.yml write_files: - path: /etc/rc.local permissions: "0755" content: | #!/bin/bash [ ! -e /usr/bin/docker ] && ln -s /usr/bin/docker.dist /usr/bin/docker rancher: services: nfs: image: d3fk/nfs-client labels: io.rancher.os.after: console, preload-user-images io.rancher.os.scope: system net: host privileged: true restart: always volumes: - /usr/bin/iptables:/sbin/iptables:ro - /mnt/docker:/mnt/docker:shared - /mnt/dbs:/mnt/dbs:shared environment: SERVER: 192.168.0.2 SHARE: /mnt/zpool/docker MOUNTPOINT: /mnt/docker #cloud-config mounts: - ["192.168.0.2:/mnt/zpool/dbs", "/mnt/dbs", "nfs", ""]
I set up rancher quite a while ago using this guide and recently updated to rancher 1.5.x from 1.0.x... without creating a snapshot first. Big mistake. Because it now appears to hang on boot. If I iohyve console into the VM it is completely unresponsive. The only way to exit is an iohyve conreset in another SSH terminal and the only stop command to which the VM reacts is iohyve forcekill. I have tried removing my grub.cfg (which uses wildcards), which causes the grub> prompt to show up as expected, but as soon as I issue the boot command the behavior is the same as before, no matter if I use the new vmlinuz and initrd or the old ones.
- The available vmlinuz files are vmlinuz-4.9.24-rancher vmlinuz-4.9.40-rancher vmlinuz-4.14.85-rancher
- The available initrd files are initrd-v1.0.1 initrd-v1.0.4 initrd-v1.5.1
- At some point after the boot rdmsr to register 0x34 on vcpu 0 appears on the SSH console from which I issued iohyve boot RancherOS, but nothing changes wrt console behavior