RancherOS v0.8.0 is now available! This release has taken a bit more time than prior versions, as we’ve been laying more groundwork to allow us to do much faster updates, and to release more often.
Using the Linux 4.9.9 mainline kernel Using the mainline stable Linux kernel should allow us to give container users access to new features faster – and will mean that RancherOS will have a simpler debug and update path for other software too.
Placing the installer container image in the ISO This change allows users to install RancherOS without internet access, and simplifies automated testability of changes. This adds about 13MB to the ISO, but means that you can do a basic install of RancherOS without pulling an image from the Docker Hub. Read more
We’re excited to announce that RancherOS is now available as a first-class operating system on Packet for all instance types. Packet is a bare metal cloud that combines the speed of physical hardware with the flexibility and ease of use of virtualized infrastructure.
We’ve always been fans of Packet and we make use of it internally quite often. In fact, we’ve recently decided to move our entire CI/CD pipeline over to Packet instances. Prior to native RancherOS support, we’ve been running it internally by booting another operating system and then running a custom installation script.
Even with this overhead we’ve had an excellent experience with Packet. After adding support for automated RAID installs and integrating with Packet’s provisioning system, we were able to create an official installation process and move away from our custom script.
The first version of RancherOS available on Packet is v0.7.0. This release brings many exciting features such as the ability to dynamically choose the Docker engine version via a cloud-config parameter and the ability to easily customize Docker daemon settings. In addition to these new features, RancherOS brings all of its traditional features to the table, such as being an order of magnitude smaller than other operating systems available on Packet.
We’d like to thank Andrew Hodges and the rest of the Packet crew for all of their help throughout this process.
Version v0.7.0 of RancherOS, which mainly contains bug fixes and enhancements, was recently released and is now available on our releases page. Since there hasn’t been a blog post since the v0.5.0 release, this post also includes some of the key features implemented as part of v0.6.0 and v0.6.1. In addition to switching the default Docker version to 1.12.1 and kernel version to 4.4.21, the following features have been implemented.
Better Support for Switching Docker Engines
It has always been part of the design of RancherOS to run two instances of Docker. The first is System Docker, which runs as PID 1 and is responsible for managing system services. The other, which we typically call User Docker or just Docker, is actually run as a container managed by System Docker. Starting with v0.6.0, the process for changing the User Docker container has been made much easier. Read more
We’ve recently released v0.5.0 of RancherOS, the latest major release since v0.4.0. Since then, we’ve moved RancherOS out of an alpha state and made many changes to improve both stability and user experience. In addition to various bug fixes and support for Docker 1.11, v0.5.0 includes the following changes:
Official Raspberry Pi Image
On our releases page you can now find an official Raspberry Pi image which is known to work on both Raspberry Pi 2 and 3. We’re especially excited about this since it offers users a cheap method of getting started with Docker and RancherOS. We’d like to thank the Hypriot team for their assistance on this feature.
Improved Build Process
Our build process has been refactored to support multiple architectures. With a given kernel, RancherOS can now be built for both ARM and ARM64 devices. In addition, the build process is now faster than it was previously which makes it easier than ever to create custom builds of RancherOS.
Console Switching without a Reboot
Switching to an alternate console can now be done without a reboot. The `ros console` subcommand was added to make this an easy process. The available consoles can be listed with `ros console list`. Ubuntu, Debian, Fedora, and CentOS consoles are currently available. The `ros console switch` command can be used to perform the switch.
Additional Configuration Options
Several additional cloud-config options were added.
`console` – Sets the console container without having to add system services
`resize_device` – Enables partition expanding with relying on a system service or network access
`mounts` – Implements the cloud-init `mounts` key, which allows a set of mounts to be specified
`sysctl` – Allows specifying sysctl settings
`registy_auths` – Configures private registry and private image authentication for system services
While the best way to check out these new features is to launch RancherOS, we’ve recorded a new demo that covers the basics of the operating system:
This is an exciting release for us to bring to our community and users. It’s great to watch RancherOS as it becomes a more stable operating system for a variety of uses. As always, we are keeping to the philosophy that RancherOS should only include the minimum necessary to get Docker up and running. To get started with RancherOS or learn more about it, check out our docs. If you have questions or issues, please head over to our Github page or to the RancherOS forums.
Today we are excited to announce a major release of RancherOS. The first release of RancherOS was announced just six months ago. At that time, powering an entire operating system with Docker was a really experimental concept. We had good reason to believe it was a good idea, but honestly we didn’t know how well it would play out and what issues we might encounter. I’m excited to say that it’s worked out great. Having said that, we felt that sometimes RancherOS could be a little difficult to grasp for new users. With RancherOS v0.4 we made a number of major enhancements to improve usability and customization. To do this we made improved support for various storage systems, made it easier to run go binaries, simplified configuration, improved the console experience, introduced a better build system, and reduced the size of the runtime footprint. Read more
Last week Ivan Mikushin discussed adding system services to RancherOS using Docker Compose. Today I want to show you an exmaple of how to deploy Linux Dash as a system service. Linux Dash is a simple, low overhead, and web supported monitoring tool for Linux, you can read more about Linux Dash here. In this post i will add Linux Dash as a system service to RancherOS version 0.3.0 which allows users to add system services using rancherctl command. The Ubuntu’s console is the only service that is currently available in RancherOS.
Creating Linux Dash Docker Image
I build a 32MB node.js busybox image on top of the hwestphal/nodebox image, with linux-dash installed which will run on port 80 by default. The Docker file of this image:
MAINTAINER Hussein Galal
RUN opkg-install unzip
RUN curl -k -L -o master.zip https://github.com/afaqurk/linux-dash/archive/master.zip
RUN unzip master.zip
RUN npm install