Containerization of apps is evermore elegant and flexible an architecture when services normally thought of as system are also loosely coupled. This extends all the way up to the kernel. For example, ssh->git_system->git_repo_data volume allows changing the security policy and/or repos with ease. A bit like the Chain of Responsibility design pattern for software. With this is mind, RancherOS makes the most sense as a container OS. Thank you. Having said that, I've trouble with a bare metal install.
The most recent .iso that even gets to a login prompt on boot was that posted Apr. 11th.
Setting networking with the default rancher:rancher account; no problem.
Creating a cloud-config.yml config seems straight forward.
The install itself, seems to go without a problem using the following command.
rancheros-install -f -d /dev/sda -c cloud-config.yml
However, things fail from there. cloud-init fails on boot. A login prompt appears though, so it seems all will be OK with a little manual networking again. Nope! Can’t login with the account used to generate the keys and setup in cloud-config.yml. The metal is now just a brick.
Might there be a single encapsulated AND tested step-by-step document with an example account?