Wikipedia

Container Linux: Difference between revisions

Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Add a link to Fedora CoreOS
No edit summary
 
(42 intermediate revisions by 31 users not shown)
Line 1:
{{short description|Linux distribution}}
{{Use mdy dates|date=August 2014}}
{{Redirect|CoreOS|its successor, Fedora CoreOS|Fedora Linux}}
{{Infobox OS
| name = Container Linux
Line 15 ⟶ 16:
| 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 = 22472512.53.0<ref>{{Cite web |date={{date|20192020-1005-15|mdy}}22 |title=CoreOS Container Linux Release Notes # Stable channel |url=https://coreos.com/releases/#stable2512.3.0 |access-date={{date2020-05-22 |2019 website=coreos.com |archive-date=2020-11-04|mdy}}11 |websitearchive-url=https://web.archive.org/web/20201111201601/https://coreos.com/releases/#2512.3.0 }}</ref>
| latest release date = {{Start date and age|20192020|1005|1522}}
| latest preview version = 22752513.2.0<ref>{{Cite web |date={{2020-05-22 |title=CoreOS Container Linux Release Notes # Beta channel |url=https://coreos.com/releases/#2513.2.0 |access-date=2020-05-22 |2019website=coreos.com |archive-10date=2020-1511-11 |mdyarchive-url=https://web.archive.org/web/20201111201601/https://coreos.com/releases/#2513.2.0}}</ref>(Beta) / {{Start date and age|2020|05|22}}<br>2514.1.0<ref>{{Cite web |date=2020-05-22 |title=CoreOS Container Linux Release Notes # Alpha channel |url=https://coreos.com/releases/#alpha2514.1.0 |access-date={{date2020-05-22 |website=coreos.com |2019archive-date=2020-11-04|mdy}}11 |websitearchive-url=https://web.archive.org/web/20201111201601/https://coreos.com/releases/#2514.1.0}}</ref>(Alpha)
| latest preview date = {{Start date and age|20192020|1005|1522}}
| working state = [[End-of-life (product)|End-of-life]] announcedDiscontinued<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 34 ⟶ 35:
| updatemodel =
| package manager =
| succeeded by = Fedora CoreOS<br>RHEL CoreOS<br>Flatcar Container Linux
| websiterepo = {{URL|https://coreosgithub.com/os/docs/latest/coreos}}
}}
 
'''Container Linux''', (formerly '''CoreOS Linux'''), wasis a andiscontinued [[Open-source software|open-source]] lightweight [[operating system]] based on the [[Linux kernel]] and designed for providing infrastructure tofor [[Computer cluster|clustered]] deployments,. while focusing on automation, easeOne of applicationits deployment,focuses security, reliability andwas [[scalability]]. As an operating system, Container Linux provided only the minimal functionality required for deploying applications inside [[software container]]s, together with built-in mechanisms for [[service discovery]] and configuration sharing.<ref name="container-linux-rename">{{Cite web
| url = https://coreos.com/blog/tectonic-self-driving.html#coreos-linux-is-now-container-linux
| title = CoreOS Linux is now Container Linux
| access-date = {{date|2016-12-20|ifuporg}} December 2016
| website = coreos.com
}}</ref><ref name="linux.com-737364">{{Cite web
| 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 = August 22, 2013
| date = {{date|2013-08-22|mdy}} | access-date = {{date|2014-03-26|mdy}}
| access-date = March 26, 2014
| website = itnews2day.com
| archive-date = November 29, 2014
}}</ref><ref name="coreos-using">{{Cite web▼
| archive-url = https://web.archive.org/web/20141129021412/http://itnews2day.com/2013/08/22/coreos-linux-based-server-systems/
▲ | url-status = dead
▲ }}</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 ⟶ 79:
| 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 OSChromeOS]], and [[Chromium OSChromiumOS]] 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
}}</ref>{{rp|7:02}} CoreOS was developed primarily by [[Alex Polvi]], Brandon Philips, and Michael Marineau,<ref name="wired-201308" /> with its major features available as a [[stable release]].<ref>{{cite web
| 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
| archive-date = November 11, 2020
}}</ref><ref>{{cite web▼
| archive-url = https://web.archive.org/web/20201111201601/https://coreos.com/releases/
▲ | url-status = dead
▲ }}</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>
 
The CoreOS team announced the [[End-of-life (product)|end-of-life]] for Container Linux on May 26, 2020,<ref name=eol /> offering [[Fedora (operating system)#CoreOS|Fedora CoreOS]],<ref>{{Cite web|title=Fedora CoreOS Documentation :: Fedora Docs Site|url=https://docs.fedoraproject.org/en-US/fedora-coreos/|access-date=2020-08-16|website=docs.fedoraproject.org}}</ref> and RHEL CoreOS as its replacement, both based on [[Red Hat Enterprise Linux|Red HatRHEL]]. CoreOS as its replacement.
 
== {{Anchor|ROCKET|APPC|ACI|OCP|OCI|RKT}}Overview ==
Line 115 ⟶ 120:
| 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 ⟶ 139:
| 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 the required properties of the ''application container image'' (ACI);. CoreOS initiatedcreated 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> aimingaimed at having themto become part of the vendor- and operating-system-independent ''Open Container Initiative,'' (or OCI;, initially named the ''Open Container Project'' or (OCP<ref>)
containerization standard,<ref>
{{cite news
| last1 = McAllister
Line 179 ⟶ 184:
| quote = Announced at the DockerCon conference in San Francisco on Monday, the Open Container Project (OCP) will maintain and develop a common container runtime and image format based in part on code and specs donated by Docker.
}}
containerization standard,</ref> which was announced{{ by whom|date=Januarya group of large tech 2017}}companies in June 2015.<ref>{{cite news▼
</ref>)
▲containerization standard, which was announced{{by whom|date=January 2017}} in June 2015.<ref>{{cite news
| 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>
 
Container Linux uses [[ebuild]] scripts from Gentoo Linux for automated [[Compiler|compilation]] of its system components,<ref name="coreos-sdk-building" /><ref name="gentoo-based" /> and uses [[systemd]] as its primary [[init]] system, with tight integration between systemd and various Container Linux's internal mechanisms.<ref name="linux.com-737364" /><ref>{{Cite web
| 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:
| 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>
 
To ensure that only a certain part of the [[Computer cluster|cluster]] reboots at once when the operating system updates are applied, preserving that way the resources required for running deployed applications, CoreOS provides ''locksmith'' as a [[Reboot (computing)|reboot]] manager for Container Linux.<ref>{{Cite web
| 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
}}</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-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 ⟶ 270:
| 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
}}</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 aan [[HTTP]]-based [[API]] that allows its integration into third-party utilities or [[deployment system]]s.<ref name="coreos-updates" /><ref>{{Cite web▼
| 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 ⟶ 301:
| 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 ⟶ 308:
| 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> Etcdetcd is also used in [[Kubernetes]] software.
 
Container Linux also provides the {{Mono|fleet}} cluster manager, which controls Container Linux's separate systemd instances at the cluster level. As of 2017, "fleet" is no longer actively developed and is deprecated in favor of [[Kubernetes]].<ref>{{cite web|last1=Wood|first1=Josh|title=Container orchestration: Moving from fleet to Kubernetes|url=https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html|website=coreos..com|publisher=CoreOS}}</ref> By using {{Mono|fleetd}}, Container Linux creates a distributed [[init|init system]] that ties together separate systemd instances and a cluster-wide {{Mono|etcd}} deployment;<ref name="lwn-617452" /> internally, {{Mono|fleetd}} daemon communicates with local {{Mono|systemd}} instances over [[D-Bus]], and with the {{Mono|etcd}} deployment through its exposed API. Using {{Mono|fleetd}} allows the deployment of single or multiple [[Software container|containers]] cluster-wide, with more advanced options including [[Redundancy (engineering)|redundancy]], [[failover]], deployment to specific cluster members, dependencies between containers, and grouped deployment of containers. A command-line utility called {{Mono|fleetctl}} is used to configure and monitor this distributed init system;<ref>{{Cite web
| 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 ⟶ 363:
| 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 373 ⟶ 369:
 
== {{Anchor|TECTONIC|FLANNEL}}Deployment ==
When running on dedicated hardware, Container Linux can be either permanently installed toon local storage, such as a [[hard disk drive]] (HDD) or [[solid-state drive]] (SSD),<ref>{{Cite web
| 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.
 
Container Linux can also be deployed through its commercial distribution called ''Tectonic'', which additionally integrates Google's [[Kubernetes]] as a cluster management utility. {{As of|2015|04}}, Tectonic is planned to be offered as [[beta software]] to select customers.<ref name="lwn-644089" /><ref>{{cite news
| url = httphttps://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>
Line 431 ⟶ 427:
{{Clear}}
 
== {{Anchor|Derivatives}}Derivatives ==
Following its acquisition of CoreOS, Inc.<ref>{{Cite web|url=https://www.cnbc.com/2018/01/30/red-hat-buys-coreos-for-250-mililon.html|title=Red Hat pays $250 million for CoreOS, a start-up that sells Google-developed technology|last=Rosoff|first=Matt|date=2018-01-30|website=CNBC|language=en|access-date=2019-06-06}}</ref> in January 2018, Red Hat announced<ref>{{Cite web|url=https://coreos.com/blog/fedora-coreos-red-hat-coreos-and-future-container-linux|title=Fedora CoreOS, Red Hat CoreOS, and the future of Container Linux {{!}} CoreOS|website=coreos.com|access-date=2019-06-06}}</ref> that it would be merging CoreOS Container Linux with Red Hat's Project Atomic, to create a new operating system, Red Hat CoreOS, while aligning the upstream Fedora Project open source community around Fedora CoreOS, combining technologies from both predecessors.
 
On March 6, 2018, Kinvolk GmbH announced Flatcar Container Linux, a derivative of CoreOS Container Linux.<ref>{{Cite web|url=https://kinvolk.io/blog/2018/03/announcing-the-flatcar-linux-project/|title=Announcing the Flatcar Linux project {{!}} Kinvolk|website=kinvolk.io|date=March 6, 2018 |access-date=2019-06-06}}</ref> [https://www.flatcar-linux.org/ Flatcar Container Linux], a derivative of CoreOS Container Linux. This tracks the upstream CoreOS alpha/, beta/, and stable channel releases, with an experimental Edge release channel added in May 2019.<ref>{{Cite web|url=https://kinvolk.io/blog/2019/05/introducing-the-flatcar-linux-edge-channel/|title=Introducing the Flatcar Linux Edge Channel {{!}} Kinvolk|website=kinvolk.io|date=May 15, 2019 |access-date=2019-06-06}}</ref>
 
== Reception ==
Line 449 ⟶ 445:
* [[Software as a service]] (SaaS){{snd}} a software licensing and delivery model that hosts the software centrally and licenses it on a subscription basis
* [[Virtualization]]{{snd}} a general concept of providing virtual versions of computer hardware platforms, operating systems, storage devices, etc.
* [[CBL-Mariner]]{{snd}} [[cloud infrastructure]] operating system based on Linux and developed by [[Microsoft]]
 
== References ==
Line 456 ⟶ 451:
== External links ==
{{Commons category|CoreOS}}
* Official {{Official website|https://coreos.com/|CoreOS}} and {{Official website|https://tectonic.com/|Tectonic}} websites, and [[GitHub]] source code repositories: {{GitHub|coreos|CoreOS|link=hidden}}, {{GitHub|coreos/etcd|etcd|link=hidden}}, {{GitHub|coreos/fleet|fleet|link=hidden}}, {{GitHub|coreos/rkt|rkt|link=hidden}} and {{GitHub|coreos/coreos-overlay|CoreOS-overlay|link=hidden}}
* {{DistroWatch|CoreOS|name=CoreOS}}
* [http://www.sebastien-han.fr/blog/2013/09/03/first-glimpse-at-coreos/ First glimpse at CoreOS], September 3, 2013, by Sébastien Han
* [httphttps://www.zdnet.com/article/coreos-linux-for-the-cloud-and-the-datacenter-7000031137/ CoreOS: Linux for the cloud and the datacenter], [[ZDNet]], July 2, 2014, by Steven J. Vaughan-Nichols
* [httphttps://www.infoworld.com/article/2692889/open-source-software/coreos-an-existential-threat-to-linux-vendors.html What's CoreOS? An existential threat to Linux vendors], ''[[InfoWorld]]'', October 9, 2014, by Matt Asay
* [httphttps://www.thecloudcast.net/2015/03/the-cloudcast-180-understanding-coreos.html Understanding CoreOS distributed architecture], March 4, 2015, a talk to Alex Polvi by Aaron Delp and Brian Gracely
* [https://github.com/coreos/fleet/blob/master/Documentation/architecture.md CoreOS fleet architecture], August 26, 2014, by Brian Waldon et al.
* [httphttps://googlecloudplatformcloudplatform.blogspotgoogleblog.com/2014/05/official-coreos-images-are-now-available-on-google-compute-engine.html Running CoreOS on Google Compute Engine], May 23, 2014
* [https://www.phoronix.com/scan.php?page=news_item&px=CoreOS-Btrfs-To-EXT4-OverlayFS CoreOS moves from Btrfs to Ext4&nbsp;+ OverlayFS], [[Phoronix]], January 18, 2015, by Michael Larabel
* [https://lwn.net/Articles/646054/ Containers and persistent data], [[LWN.net]], May 28, 2015, by Josh Berkus
* [https://www.flatcar-linux.org/ Flatcar Container Linux]
 
{{Linux distributions}}{{Virtualization software}}
{{Linux}}
{{Linux kernel}}
{{Linux containers}}
[[Category:Linux Containerizationdistributions]]▼
 
[[Category:Enterprise Linux distributions]]
[[Category:Linux containerization]]
[[Category:Containerization software]]
▲[[Category:Linux Containerization]]
[[Category:Operating systems based on the Linux kernel]]
[[Category:Red Hat software]]
[[Category:Software using the Apache license]]
[[Category:Virtualization-related software for Linux]]
[[Category:X86-64 operating systems]]
Retrieved from "https://en.wikipedia.org/wiki/Container_Linux"