Skip to main content

Over the last few hours we began rolling out shellshock fixes to all CoreOS deploys that have automatic updates enabled (this is default). If you have disabled automatic upgrades through cloud-config reboot-strategy, a manual reboot should give you the latest version.

You can test if your CoreOS has been patched by testing the exploit, or by checking the version of CoreOS you are running in /etc/os-release. Patched versions are listed below:

As many of you have heard, there are open Bash vulnerabilities, CVE-2014-6271, and CVE-2014-7169. The common vectors for arbitrary code execution from these CVEs include: bash exposed via certain web applications and dhcpcd scripts. Additionally, SSH accounts restricted by the command= option in their ssh key can bypass that restriction.

Yesterday we were excited to see that Interactive Markdown, who used CoreOS on DigitalOcean, won runner up at the TechCrunch Disrupt hackathon. CoreOS was made available on DigitalOcean on Friday and come Saturday the Interactive Markdown team was building their application on top of CoreOS.

2,000 of you voted for CoreOS on DigitalOcean and we're happy to report that it's arrived. Starting today, you can head to DigitalOcean, choose the CoreOS image, and start experimenting with containers and all CoreOS has to offer.

Edit: This post has been updated to reflect the project name change from rudder to flannel

This is a guest post by Lucas Carlson, Head of CenturyLink Labs

Here at CenturyLink Labs, we help people learn how to adopt new technologies like Docker and CoreOS into their daily lives. This has given us a unique perspective on the Docker ecosystem because we are trying to stay on top of one of the fastest growing open-source projects in history.

After talking to tens of thousands of developers and ops people, we kept hearing the same thing over and over:

Update: We've updated a few aspects of our training program and the CoreOS Specialist certification is not offered at this time.

Today we are excited to bring you more opportunities to learn about CoreOS - both through the Linux Foundation’s Certification Program that was announced today and through in-person training courses.

Today we announced that Quay.io is now part of the CoreOS family. If you are not familiar with Quay.io, it is the first hosted private docker registry. In addition to continuing to invest in Quay.io, we are launching the CoreOS Enterprise Registry based on Quay.io. Enterprise Registry is a solution for companies that want to run their own docker registry.

 

Today we announced that Quay.io is now part of the CoreOS family. If you are not familiar with Quay.io, it is the first hosted private docker registry. In addition to continuing to invest in Quay.io, we are launching the CoreOS Enterprise Registry based on Quay.io. Enterprise Registry is a solution for companies that want to run their own docker registry.

Edit: The most up to date Kubernetes + CoreOS guide can be found on the Kubernetes GitHub project.

In the previous post I outlined how to set up a single node Kubernetes cluster manually. This was a great way to get started and try out the basic Kubernetes examples. Now its time to take it up a notch.

Subscribe to CoreOS Blog