Wikipedia

Container Linux: Difference between revisions

Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Link to Fedora CoreOS explanation in Fedora page
m replace {{date}} in cs1|2 date-holding parameters; evaluated 73 templates; 110 parameter values modified; removed redundant |df= (3×); del |url-status= (11×);
Line 15:
| ui =
| family = [[Linux]] (based on [[Gentoo Linux]])
| released = {{Start date and age|2013|10|03}}<ref>{{Cite web |date={{date|October 3, 2013-10-03|mdy}} |title=coreos/manifest: Release v94.0.0 (Container Linux v94.0.0) |url=https://github.com/coreos/manifest/releases/tag/v94.0.0 |access-date={{date|September 22, 2014-09-22|mdy}} |website=github.com}}</ref>
| latest release version = 2247.5.0<ref>{{Cite web |date={{date|October 15, 2019-10-15|mdy}} |title=CoreOS Container Linux Release Notes # Stable channel |url=https://coreos.com/releases/#stable |access-date={{date|November 4, 2019-11-04|mdy}} |website=coreos.com}}</ref>
| latest release date = {{Start date and age|2019|10|15}}
| latest preview version = 2275.2.0<ref>{{Cite web |date={{date|October 15, 2019-10-15|mdy}} |title=CoreOS Container Linux Release Notes # Alpha channel |url=https://coreos.com/releases/#alpha |access-date={{date|November 4, 2019-11-04|mdy}} |website=coreos.com}}</ref>
| latest preview date = {{Start date and age|2019|10|15}}
| working state = Discontinued<ref name=eol>{{Cite web|title=End-of-life announcement for CoreOS Container Linux|url=https://coreos.com/os/eol/|access-date=2020-08-16|website=coreos.com|language=en}}</ref>
| license = [[Apache License&nbsp;2.0]]<ref>{{Cite web |date={{date|March 13, 2014-03-13|mdy}} |title=CoreOS Pilot Agreement |url=https://coreos.com/legal/pilot/ |url-status=dead |archive-url=https://web.archive.org/web/20140912161231/https://coreos.com/legal/pilot/ |archive-date=September 12, 2014 |access-date={{date|2014-03-March 26|mdy}}, 2014 |website=coreos.com |df=mdy-all}}</ref><ref name="license-etcd">{{Cite web
| url = https://github.com/coreos/etcd/blob/master/LICENSE
| title = coreos/etcd: etcd/LICENSE at master
| date = {{date|2013-07-July 31|mdy}}, 2013 | access-date = {{date|March 26, 2014-03-26|mdy}}
| website = github.com
}}</ref>
Line 46:
| url = http://www.linux.com/news/featured-blogs/200-libby-clark/737364-brandon-philips-how-the-coreos-linux-distro-uses-cgroups
| title = Brandon Philips: How the CoreOS Linux Distro Uses Cgroups
| date = {{date|September 9, 2013-09-09|mdy}}
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| author = Libby Clark
| publisher = [[Linux.com]]
| archive-url = https://web.archive.org/web/20140222051301/http://www.linux.com/news/featured-blogs/200-libby-clark/737364-brandon-philips-how-the-coreos-linux-distro-uses-cgroups
| archive-date = February 22, 2014
| url-status = dead
}}</ref><ref name="wired-201308">{{cite magazine
| url = https://www.wired.com/wiredenterprise/2013/08/coreos-the-new-linux/
| title = Linux Hackers Rebuild Internet From Silicon Valley Garage
| date = {{date|2013-08-August 21|mdy}}, 2013 | access-date = {{date|February 13, 2014-02-13|mdy}}
| author = Cade Metz | magazine = [[Wired (magazine)|Wired]]
}}</ref><ref name="itnews2day">{{Cite web
| url = http://itnews2day.com/2013/08/22/coreos-linux-based-server-systems/
| title = CoreOS – a new approach to Linux-based server systems
| date = {{date|2013-08-August 22|mdy}}, 2013 | access-date = {{date|March 26, 2014-03-26|mdy}}
| website = itnews2day.com
}}</ref><ref name="coreos-using">{{Cite web
| url = https://coreos.com/using-coreos/
| title = CoreOS documentation: Using CoreOS
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
| archive-url = https://web.archive.org/web/20140223040854/https://coreos.com/using-coreos/
| archive-date = February 23, 2014
| url-status = dead
}}</ref>
 
Line 76 ⟶ 74:
| url = https://coreos.com/os/docs/latest/sdk-building-development-images.html#updating-portage-stable-ebuilds-from-gentoo
| title = Building development images: Updating portage-stable ebuilds from Gentoo
| access-date = {{date|2016-05-May 24|mdy}}, 2016
| website = coreos.com
| archive-url = https://web.archive.org/web/20170714053215/https://coreos.com/os/docs/latest/sdk-building-development-images.html#updating-portage-stable-ebuilds-from-gentoo
| archive-date = July 14, 2017
| url-status = dead
}}</ref><ref name="gentoo-based">{{cite web
| url = https://wiki.gentoo.org/wiki/Distributions_based_on_Gentoo
| title = Distributions based on Gentoo
| date = {{date|2016-03-March 25|mdy}}, 2016 | access-date = {{date|May 24, 2016-05-24|mdy}}
| website = gentoo.org
}}</ref> [[Chrome OS]], and [[Chromium OS]] through a common [[software development kit]] (SDK). Container Linux adds new functionality and customization to this shared foundation to support server hardware and use cases.<ref name="itnews2day" /><ref>{{cite web
| url = https://www.youtube.com/watch?v=JeICd9XyXfY&t=422
| title = CoreOS: Anatomy of a CoreOS update
| date = {{date|July 8, 2014-07-08|mdy}} | access-date = {{date|July 25, 2014-07-25|mdy}}
| author = Brian Harrington | publisher = Rackspace
| website = youtube.com
Line 95 ⟶ 92:
| url = https://coreos.com/blog/stable-release/
| title = CoreOS Stable Release
| date = {{date|2014-07-July 25|mdy}}, 2014 | access-date = {{date|August 28, 2014-08-28|mdy}}
| author = Alex Polvi | website = coreos.com
}}</ref><ref>{{cite web
| url = https://coreos.com/releases/
| title = CoreOS Release Notes
| access-date = {{date|2014-08-August 28|mdy}}, 2014
| website = coreos.com
}}</ref><ref>{{cite web
| url = https://coreos.com/blog/etcd-2.0-release-first-major-stable-release/
| title = etcd&nbsp;2.0 Release – First Major Stable Release
| date = {{date|2015-01-January 28|mdy}}, 2015 | access-date = {{date|June 14, 2015-06-14|mdy}}
| author = Brandon Philips | website = coreos.com
}}</ref>
Line 115 ⟶ 112:
| url = https://lwn.net/Articles/256389/
| title = Notes from a container
| date = {{date|2007-10-October 29|mdy}}, 2007 | access-date = {{date|July 3, 2016-07-03|mdy}}
| author = Jonathan Corbet | publisher = [[LWN.net]]
}}</ref><ref>{{Cite web
| url = https://lwn.net/Articles/621006/
| title = Control group namespaces
| date = {{date|2014-11-November 19|mdy}}, 2014 | access-date = {{date|July 3, 2016-07-03|mdy}}
| author = Jake Edge | publisher = [[LWN.net]]
}}</ref> which together provide abilities to limit, account and isolate resource usage ([[CPU]], memory, disk [[I/O]], etc.) for the collections of userspace [[Process (computing)|processes]].<ref name="linux.com-737364" /><ref name="coreos-using" /><ref name="coreos-containers">{{Cite web
| url = https://coreos.com/using-coreos/containers/
| title = CoreOS documentation: Using Docker with CoreOS
| access-date = {{date|2015-06-June 14|mdy}}, 2015
| website = coreos.com
| archive-url = https://web.archive.org/web/20160804005603/https://coreos.com/using-coreos/containers/
| archive-date = August 4, 2016
| url-status = dead
}}</ref>
 
Line 135 ⟶ 131:
| url = http://blog.docker.com/2014/03/docker-0-9-introducing-execution-drivers-and-libcontainer/
| title = Docker 0.9: Introducing execution drivers and libcontainer
| date = {{date|2014-03-March 10|mdy}}, 2014 | access-date = {{date|January 20, 2015-01-20|mdy}}
| website = docker.com
}}</ref> to the operating-system-level virtualization features of the Linux kernel, as well as providing a standardized format for containers that allows applications to run in different environments.<ref name="linux.com-737364" /><ref name="coreos-containers" /> In December 2014, CoreOS released and started to support ''rkt'' (initially released as ''Rocket'') as an alternative to Docker, providing through it another standardized format of the application-container images, the related definition of the container [[runtime environment]], and a [[Communications protocol|protocol]] for discovering and retrieving container images.<ref>{{Cite web
| url = https://www.linux.com/news/featured-blogs/200-libby-clark/806347-collaboration-summit-keynote-alex-polvi-coreos
| title = CoreOS Co-Founder Alex Polvi Talks Containers, Rocket vs. Docker, and More
| date = {{date|2015-01-January 30|mdy}}, 2015 | access-date = {{date|June 14, 2015-06-14|mdy}}
| author = Libby Clark | publisher = [[Linux.com]]
}}</ref><ref>{{Cite web
| url = http://www.informationweek.com/cloud/infrastructure-as-a-service/rocket-containers-how-coreos-plans-to-challenge-docker/d/d-id/1319167
| title = Rocket Containers: How CoreOS Plans To Challenge Docker
| date = {{date|2015-02-February 20|mdy}}, 2015 | access-date = {{date|June 14, 2015-06-14|mdy}}
| author = Charles Babcock | website = informationweek.com
}}</ref><ref>{{Cite web
| url = https://coreos.com/blog/rocket/
| title = CoreOS is building a container runtime, rkt
| date = {{date|December 1, 2014-12-01|mdy}} | access-date = {{date|June 14, 2015-06-14|mdy}}
| author = Alex Polvi | website = coreos.com
}}</ref><ref name="lwn-631630">{{Cite web
| url = https://lwn.net/Articles/631630/
| title = New etcd, appc, and Rocket releases from CoreOS
| date = {{date|February 4, 2015-02-04|mdy}} | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Josh Berkus | publisher = [[LWN.net]]
}}</ref> CoreOS provides rkt as an implementation of the so-called ''app container'' (appc) specification that describes required properties of the ''application container image'' (ACI); CoreOS initiated appc and ACI as an independent committee-steered set of specifications,<ref name="lwn-644089">{{Cite web
| url = https://lwn.net/Articles/644089/
| title = CoreOS Fest and the world of containers, part 1
| date = {{date|2015-05-May 13|mdy}}, 2015 | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Josh Berkus | publisher = [[LWN.net]]
}}</ref><ref>{{Cite web
| url = https://lwn.net/Articles/624349/
| title = The Rocket containerization system
| date = {{date|December 3, 2014-12-03|mdy}} | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Nathan Willis | publisher = [[LWN.net]]
}}</ref> aiming at having them become part of the vendor- and operating-system-independent ''Open Container Initiative'' (OCI; initially named the ''Open Container Project'' or OCP<ref>
Line 183 ⟶ 179:
| url = https://techcrunch.com/2015/06/22/docker-coreos-google-microsoft-amazon-and-others-agree-to-develop-common-container-standard/
| title = Docker, CoreOS, Google, Microsoft, Amazon and others come together to develop common container standard
| date = {{date|2015-06-June 22|mdy}}, 2015 | access-date = {{date|June 24, 2015-06-24|mdy}}
| author = Frederic Lardinois | work = [[TechCrunch]]
}}</ref><ref>{{Cite web
| url = https://www.opencontainers.org/pressrelease/
| title = Industry Leaders Unite to Create Project for Open Container Standards
| date = {{date|2015-06-June 22|mdy}}, 2015
| access-date = {{date|2015-06-June 24|mdy}}, 2015
| website = opencontainers.org
| url-status = dead
| archive-url = https://web.archive.org/web/20150813223334/https://www.opencontainers.org/pressrelease/
| archive-date = August 13, 2015
| df = mdy-all
}}</ref><ref>{{cite web
| url = https://www.theregister.co.uk/2015/07/22/open_container_status_update/
| title = Open Container Project renames, says standard is just weeks away: Linux Foundation, Docker and friends opt for Open Container Initiative
| date = {{date|2015-07-July 22|mdy}}, 2015 | access-date = {{date|January 29, 2016-01-29|mdy}}
| author = Neil McAllister | website = [[The Register]]
}}</ref>
Line 205 ⟶ 199:
| url = https://coreos.com/using-coreos/systemd/
| title = CoreOS documentation: Using systemd with CoreOS
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
| url-status = dead
| archive-url = https://web.archive.org/web/20140214143636/https://coreos.com/using-coreos/systemd/
| archive-date = February 14, 2014
| df = mdy-all
}}</ref>
 
Line 217 ⟶ 209:
| url = https://coreos.com/using-coreos/updates/
| title = CoreOS documentation: Updates & patches
| access-date = {{date|2015-02-February 27|mdy}}, 2015
| website = coreos.com
| archive-url = https://web.archive.org/web/20140214150559/https://coreos.com/using-coreos/updates/
| archive-date = February 14, 2014
| url-status = dead
}}</ref> The root partition and its [[root file system]] are automatically resized to fill all available disk-space upon reboots; while the root partition provides read-write storage space, the operating system itself is [[Mount (computing)|mounted]] read-only under {{Mono|/usr}}.<ref name="activestate">{{Cite web
| url = http://www.activestate.com/blog/2013/08/alex-polvi-explains-coreos
| title = Alex Polvi Explains CoreOS
| date = {{date|2013-08-August 28|mdy}}, 2013
| access-date = {{date|May 7, 2015-05-07|mdy}}
| author = Phil Whelan
| website = activestate.com
| archive-url = https://web.archive.org/web/20150224184727/http://www.activestate.com/blog/2013/08/alex-polvi-explains-coreos
| archive-date = February 24, 2015
| url-status = dead
}}</ref><ref>{{Cite web
| url = https://coreos.com/docs/cluster-management/scaling/adding-disk-space/
| title = CoreOS documentation: Adding disk space to your CoreOS machine
| access-date = {{date|2015-02-February 27|mdy}}, 2015
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://coreos.com/blog/new-filesystem-btrfs-cloud-config/
| title = Major Update: btrfs, Docker&nbsp;0.9, add users, writable /etc, and more!
| date = {{date|2014-03-March 27|mdy}}, 2014 | access-date = {{date|February 27, 2015-02-27|mdy}}
| author = Alex Polvi | website = coreos.com
}}</ref>
Line 247 ⟶ 237:
| url = http://www.centurylinklabs.com/interviews/simple-introduction-to-coreos-with-ceo-alex-polvi-and-cto-brandon-philips/
| title = Simple Introduction to CoreOS with CEO Alex Polvi and CTO Brandon Philips
| date = {{date|June 6, 2014-06-06|mdy}}
| access-date = {{date|2015-06-June 22|mdy}}, 2015
| website = centurylinklabs.com
| archive-url = https://web.archive.org/web/20150622162656/http://www.centurylinklabs.com/interviews/simple-introduction-to-coreos-with-ceo-alex-polvi-and-cto-brandon-philips/
| archive-date = June 22, 2015
| url-status = dead
}}</ref> Using locksmith, one can select between different update strategies that are determined by how the reboots are performed as the last step in applying updates; for example, one can configure how many cluster members are allowed to reboot simultaneously. Internally, locksmith operates as the {{Mono|locksmithd}} [[Daemon (computing)|daemon]] that runs on cluster members, while the {{Mono|locksmithctl}} [[command-line]] utility manages configuration parameters.<ref>{{Cite web
| url = https://coreos.com/docs/cluster-management/setup/update-strategies/
| title = CoreOS documentation: Update strategies
| access-date = {{date|2015-04-April 17|mdy}}, 2015
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://github.com/coreos/locksmith/blob/master/README.md
| title = coreos/locksmith: locksmith/README.md at master
| date = {{date|February 1, 2015-02-01|mdy}} | access-date = {{date|April 17, 2015-04-17|mdy}}
| website = github.com
}}</ref> Locksmith is written in the [[Go language]] and distributed under the terms of the [[Apache License 2.0]].<ref>{{Cite web
| url = https://github.com/coreos/locksmith/blob/master/LICENSE
| title = coreos/locksmith: locksmith/LICENSE at master
| date = {{date|2014-01-January 19|mdy}}, 2014 | access-date = {{date|April 17, 2015-04-17|mdy}}
| website = github.com
}}</ref>
Line 273 ⟶ 262:
| url = http://www.nextplatform.com/2015/02/25/coreos-hyperscales-linux-by-making-it-invisible/
| title = CoreOS Hyperscales Linux By Making It Invisible
| date = {{date|2015-02-February 15|mdy}}, 2015 | access-date = {{date|June 14, 2015-06-14|mdy}}
| author = Timothy Prickett Morgan | website = nextplatform.com
}}</ref><ref>{{Cite web
| url = https://code.google.com/p/omaha/
| title = Omaha – software installer and auto-updater for Windows
| access-date = {{date|2014-10-October 11|mdy}}, 2014
| website = code.google.com
}}</ref><ref>{{Cite web
| url = http://omaha.googlecode.com/svn/wiki/OmahaOverview.html
| title = Omaha Overview
| date = {{date|2009-09-September 23|mdy}}, 2009
| access-date = {{date|2014-10-October 11|mdy}}, 2014
| website = omaha.googlecode.com
| archive-url = https://web.archive.org/web/20090506062328/http://omaha.googlecode.com/svn/wiki/OmahaOverview.html
| archive-date = May 6, 2009
| url-status = dead
}}</ref> Additionally, CoreOS provides ''CoreUpdate'' as a web-based [[Dashboard (management information systems)|dashboard]] for the management of cluster-wide updates. Operations available through CoreUpdate include assigning cluster members to different groups that share customized update policies, reviewing cluster-wide breakdowns of Container Linux versions, stopping and restarting updates, and reviewing recorded update logs. CoreUpdate also provides a [[HTTP]]-based [[API]] that allows its integration into third-party utilities or [[deployment system]]s.<ref name="coreos-updates" /><ref>{{Cite web
| url = https://godoc.org/github.com/coreos/go-omaha/omaha
| title = Package omaha
| date = {{date|2014-06-June 24|mdy}}, 2014 | access-date = {{date|July 4, 2014-07-04|mdy}}
| website = godoc.org
}}</ref><ref>{{Cite web
| url = https://coreos.com/products/coreupdate/
| title = CoreOS documentation: CoreUpdate
| access-date = {{date|July 4, 2014-07-04|mdy}}
| website = coreos.com
}}</ref>
Line 305 ⟶ 293:
| url = https://github.com/MarkMoudy/coreos-docker-CI-demo
| title = CoreOS&nbsp;+ Docker Development Environment Demo
| date = {{date|2014-05-May 16|mdy}}, 2014 | access-date = {{date|April 16, 2015-04-16|mdy}}
| author = Mark Moudy | website = github.com
}}</ref>]]
Line 312 ⟶ 300:
| url = https://lwn.net/Articles/617452/
| title = Etcd and fleet
| date = {{date|2014-10-October 22|mdy}}, 2014 | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Jonathan Corbet | publisher = [[LWN.net]]
}}</ref> Beside the configuration management, {{Mono|etcd}} also provides [[service discovery]] by allowing deployed applications to announce themselves and the services they offer. Communication with {{Mono|etcd}} is performed through an exposed [[REST]]-based API, which internally uses [[JSON]] on top of HTTP; the API may be used directly (through {{Mono|[[cURL|curl]]}} or {{Mono|[[wget]]}}, for example), or indirectly through {{Mono|etcdctl}}, which is a specialized command-line utility also supplied by CoreOS.<ref name="linux.com-737364" /><ref name="coreos-using" /><ref>{{Cite web
| url = https://coreos.com/using-coreos/etcd/
| title = CoreOS documentation: Using etcd with CoreOS
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://coreos.com/docs/cluster-management/setup/getting-started-with-etcd/
| title = CoreOS documentation: Getting started with etcd
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://speakerdeck.com/philips/etcd-at-gosf
| title = etcd @ GoSF
| date = {{date|2014-01-January 15|mdy}}, 2014 | access-date = {{date|February 13, 2014-02-13|mdy}}
| author = Brandon Philips | website = speakerdeck.com
}}</ref> Etcd is also used in [[Kubernetes]] software.
Line 334 ⟶ 322:
| url = https://www.digitalocean.com/community/tutorials/how-to-use-fleet-and-fleetctl-to-manage-your-coreos-cluster
| title = How To Use Fleet and Fleetctl to Manage your CoreOS Cluster
| date = {{date|2014-09-September 12|mdy}}, 2014 | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Justin Ellingwood | website = digitalocean.com
}}</ref> internally, it communicates with the {{Mono|fleetd}} daemon using a JSON-based API on top of HTTP, which may also be used directly. When used locally on a cluster member, {{Mono|fleetctl}} communicates with the local {{Mono|fleetd}} instance over a [[Unix ___domain socket]]; when used from an external host, [[SSH tunnel]]ing is used with authentication provided through [[public SSH key]]s.<ref>{{Cite web
| url = https://coreos.com/docs/launching-containers/launching/launching-containers-fleet/
| title = CoreOS documentation: Launching containers with fleet
| access-date = {{date|April 3, 2014-04-03|mdy}}
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://coreos.com/docs/launching-containers/launching/fleet-using-the-client/
| title = CoreOS documentation: Using the client
| access-date = {{date|April 3, 2014-04-03|mdy}}
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://github.com/coreos/fleet/blob/master/README.md
| title = coreos/fleet: fleet/README.md at master
| date = {{date|2014-02-February 18|mdy}}, 2014 | access-date = {{date|April 3, 2014-04-03|mdy}}
| website = github.com
}}</ref><ref>{{Cite web
| url = https://github.com/coreos/fleet/blob/master/Documentation/deployment-and-configuration.md
| title = coreos/fleet: fleet/Documentation/deployment-and-configuration.md at master (Deploying fleet)
| date = {{date|2015-04-April 14|mdy}}, 2015 | access-date = {{date|April 17, 2015-04-17|mdy}}
| website = github.com
}}</ref><ref>{{Cite web
| url = https://github.com/coreos/fleet/blob/master/Documentation/api-v1.md
| title = coreos/fleet: fleet/Documentation/api-v1.md (fleet API v1)
| date = {{date|2014-10-October 29|mdy}}, 2014 | access-date = {{date|April 17, 2015-04-17|mdy}}
| website = github.com
}}</ref>
Line 367 ⟶ 355:
| url = https://github.com/coreos/fleet/blob/master/LICENSE
| title = coreos/fleet: fleet/LICENSE at master
| date = {{date|February 6, 2014-02-06|mdy}} | access-date = {{date|April 3, 2014-04-03|mdy}}
| website = github.com
}}
Line 376 ⟶ 364:
| url = https://coreos.com/docs/running-coreos/bare-metal/installing-to-disk/
| title = CoreOS documentation: Installing CoreOS to disk
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
}}</ref> or booted remotely [[Network booting|over a network]] using [[Preboot Execution Environment]] (PXE) in general, or [[iPXE]] as one of its implementations.<ref>{{Cite web
| url = https://coreos.com/docs/running-coreos/bare-metal/booting-with-pxe/
| title = CoreOS documentation: Booting CoreOS via PXE
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
}}</ref><ref>{{Cite web
| url = https://coreos.com/docs/running-coreos/bare-metal/booting-with-ipxe/
| title = CoreOS documentation: Booting CoreOS via iPXE
| access-date = {{date|2014-02-February 13|mdy}}, 2014
| website = coreos.com
}}</ref> CoreOS also supports deployments on various [[hardware virtualization]] platforms, including [[Amazon Elastic Compute Cloud|Amazon EC2]], [[DigitalOcean]], [[Google Compute Engine]], [[Microsoft Azure]], [[OpenStack]], [[QEMU]]/[[Kernel-based Virtual Machine|KVM]], [[Vagrant (software)|Vagrant]] and [[VMware]].<ref name="coreos-using" /><ref>{{Cite web
| url = https://coreos.com/blog/digital-ocean-supports-coreos/
| title = CoreOS Image Now Available On DigitalOcean
| date = {{date|September 5, 2014-09-05|mdy}} | access-date = {{date|September 5, 2014-09-05|mdy}}
| author = Alex Crawford | website = coreos.com
}}</ref><ref>{{cite web
| url = https://www.theregister.co.uk/2014/05/23/google_loads_coreos_onto_its_cloud/
| title = Google brings futuristic Linux software CoreOS onto its cloud
| date = {{date|2014-05-May 23|mdy}}, 2014 | access-date = {{date|May 26, 2014-05-26|mdy}}
| author = Jack Clark | website = [[The Register]]
}}</ref><ref>{{Cite web
| url = https://coreos.com/blog/coreos-available-on-azure/
| title = CoreOS Now Available On Microsoft Azure
| date = {{date|2014-10-October 20|mdy}}, 2014 | access-date = {{date|October 22, 2014-10-22|mdy}}
| author = Alex Crawford | website = coreos.com
}}</ref> Container Linux may also be installed on Citrix XenServer, noting that a "template" for CoreOS exists.
Line 408 ⟶ 396:
| url = http://www.zdnet.com/article/coreos-is-bringing-googles-kubernetes-to-the-enterprise/
| title = CoreOS is bringing Google's Kubernetes to the enterprise
| date = {{date|April 6, 2015-04-06|mdy}} | access-date = {{date|April 29, 2015-04-29|mdy}}
| author = Steven J. Vaughan-Nichols | work = [[ZDNet]]
}}</ref><ref>{{cite magazine
| url = https://www.forbes.com/sites/benkepes/2015/04/06/coreos-and-google-make-their-defensive-plays-is-docker-the-victim/
| title = CoreOS And Google Make Their Defensive Plays, Is Docker The Victim?
| date = {{date|April 6, 2015-04-06|mdy}} | access-date = {{date|April 29, 2015-04-29|mdy}}
| author = Ben Kepes | magazine = [[Forbes]]
}}</ref> Furthermore, CoreOS provides ''Flannel'' as a component implementing an [[overlay network]] required primarily for the integration with Kubernetes.<ref name="lwn-644089" /><ref>{{Cite web
| url = https://coreos.com/blog/introducing-rudder/
| title = Introducing flannel: An etcd-backed overlay network for containers
| date = {{date|2014-08-August 28|mdy}}, 2014 | access-date = {{date|June 22, 2015-06-22|mdy}}
| author = Eugene Yakubovich | website = coreos.com
}}</ref><ref>{{Cite web
| url = http://www.slideshare.net/lorispack/using-coreos-flannel-for-docker-networking
| title = Tutorial on using CoreOS Flannel for Docker
| date = November 2014 | access-date = {{date|2015-06-June 22|mdy}}, 2015
| website = slideshare.net
}}</ref>
Retrieved from "https://en.wikipedia.org/wiki/Container_Linux"