Continental Innovates with Rancher and Kubernetes
Learn more about the steps of installing Docker on Windows, and explore the similarities and differences between Windows docker containers and Linux containers.
RancherOS v1.1.0 is [now available]! It includes a number of key enhancements such as: VMWare ESXi support; improved OS level logging, including boot-time logs; remote Syslog logging; and built in Logrotate and Cron services. Syslinux support has improved with the addition of a boot menu, allowing you to select debug, autologin, and recovery consoles. The reboot command can kexec into the latest and previous OS versions. With RancherOS v1.1.0 you still select Docker engines between 1.
containerd is an industry-standard core container runtime that was initially released by Docker Inc. in December 2015 and contributed to CNCF in March 2017. We’ve received a number of questions about the project, so I thought I would provide you my perspective as well as some preliminary thoughts on how how Rancher Labs will leverage it.
Docker, Kubernetes, and containerd The containerd project represents an important step in the evolution of the Docker platform.
This week, the Moby Project was introduced with the idea of componentizing Docker into a series of assemblies. At DockerCon, a neat demo was done using the moby tool to assemble various components into customized Linux operating system images. While very cool, this seemed to have confused people – we’d like to provide some more background and explanation about the Moby Project and how it affects Rancher, RancherOS, and our users.
RancherOS eliminates any unnecessary libraries and services, resulting in a footprint three times smaller than that of other container operating systems.
If you’re headed to Pasadena, California this weekend for Scale15x, come see us! We’re excited to be presenting, and our talks are focused on practical knowledge for running containers and Kubernetes in production. While Rancher makes it easy to deploy and manage containers and Kubernetes, building that ease of use has required specific expertise and disciplined thought on how teams are incorporating them into their projects today. We’re headed to Scale to share what we’ve learned, and to get feedback from you.
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.
Release Highlights 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.
Open source container management company exceeds revenue goals by twenty percent, reports 19 million software downloads. Cupertino, Calif. – January 25, 2017 – Rancher Labs, a provider of container management software, today announced momentum in 2016, doubling its employees, exceeding revenue targets by twenty percent and surpassing 19 million software downloads. This growth underscores the heavy demand for its popular open source software that simplifies the deployment and running of containers in production, on any infrastructure.
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.
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.
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.
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.
Hello, I’m Ivan Mikushin (@imikushin), one of the developers here at Rancher working on RancherOS. Today I wanted to walk you through the concept of RancherOS \“system services.\” As you may know, RancherOS was designed from the ground up to run everything above the kernel as Docker containers, allowing simple upgrades and a tiny OS footprint. The goal of RancherOS is to provide the perfect small OS for running Docker containers.
Today we announced Series A funding and officially launched our company Rancher Labs. We started Rancher Labs because we saw the benefits of running Docker containers in production and wanted to build tools to help make it happen. We are building two open source software products: Rancher and RancherOS. Rancher is a container infrastructure platform designed to make it simple to operate Docker in production. RancherOS is a minimal Linux distribution designed specifically for running Docker.
Nagios is a fantastic monitoring tool, and I wanted to see if I could get the agent to run as a system container on RancherOS, in order to monitor the host and any Docker containers running on it. It turned out to be incredibly easy. In this blog post, I’ll walk through how to launch the Nagios agent as system container in RancherOS. Specifically, I’ll use two vagrant boxes to cover:
Recently I have been playing around with Riak and I wanted to get it running with Docker, using RancherOS and Rancher. If you’re not familiar with Riak, it is a distributed key/value store which is designed for high availability, fault tolerance, simplicity, and near-linear scalability. Riak is written in Erlang programming language and it runs on an Erlang virtual machine. Riak provides availability through replication and faster operations and more capacity through partitions, using the ring design to its cluster, hashed keys are partitioned by default to 64 partitions (or vnodes), each vnode will be assigned to one physical node as following: From Relational to Riak Whitepaper For example, if the cluster consists of 4 nodes: Node1, Node2, Node3, and Node4, we will count around the nodes assigning each vnode to a physical node until the all vnodes are accounted for, so in the previous figure, Riak used 32 partition with 4 node cluster so we get:
Yesterday we hosted our first Rancher online meetup, which was focused on how to get started with RancherOS. For those of you who weren’t able to attend our first online meetup on March 31st, we’ve posted a recording. The meetup ran for more than two hours, and included demos of RancherOS and Rancher, as well as dozens of questions about current capabilities and some of the features we’re still working on.
This week we released Rancher 0.12, which adds support for provisioning hosts using Docker Machine. We’re really excited to get this feature out, because it makes launching Rancher-enabled Docker hosts easier than ever. If you’re not familiar with Docker Machine, it is a project that allows cloud providers to develop standard \“drivers\” for provisioning cloud infrastructure on the fly. You can learn more about it on the Docker website. The first cloud we’re supporting with Docker Machine is Digital Ocean.
This week we released RancherOS 0.2, which introduces support for upgrades. RancherOS is a tiny Linux distribution designed specifically to run Docker, using containers to isolate user and system processes. Given that RancherOS does just about everything with containers, it shouldn’t be a surprise that upgrading a RancherOS node is almost exactly like upgrading a Docker container. All of the upgrade procedures in RancherOS are accessed through the \“rancherctl\” system service.
One of the exciting things about RancherOS is the concept of running system services as containers. It offers the chance to clearly delineate between containers running an application, and containers running agents and operating system services. This has some interesting potential implications for managing operations, such as making patching and upgrading system services simpler, setting app and organizational policies for required services, and prioritizing which services have access to system resources.
Hi, I’m James Harris, (@sir_yogi_bear) one of the engineers here @Rancher_Labs, and I am excited to announce we added support this week for pulling and viewing Docker logs in Rancher. The addition of the feature allows users to easily work with their containers from the web UI in a much more involved way. Previously, there was no way to track the output of a container through Rancher. Now you can easily follow both the Std out and Std error of a container.