Fork me on GitHub

Distro Ratings

Linux/Unix distribution ratings updated on 2019-05-27

Rank Name
#1 Arch Linux
#2 Debian
#3 Ubuntu
#4 Gentoo
#5 NixOS
#6 FreeBSD
#7 OpenBSD
#8 Fedora
#9 pfSense
#10 CentOS
#11 FreeNAS
#12 Alpine Linux
#13 Red Hat Enterprise Linux
#14 NetBSD
#15 Devuan
#16 Linux Mint
#17 Kubuntu
#18 Guix
#19 Void Linux
#20 Qubes OS
#21 Proxmox
#22 openSUSE
#23 slackware
#24 Raspbian
#25 Kali Linux
#26 illumos
#27 manjaro
#28 haiku
#29 SmartOS
#30 kde-neon
#31 OPNsense
#32 CoreOS
#33 libreelec
#34 Solus
#35 xubuntu
#36 funtoo
#37 reactos
#38 freeswitch
#39 dragonflybsd
#40 vyos
#41 antergos
#42 omnios
#43 calculate
#44 lubuntu
#45 parabola
#46 exherbo
#47 blackarch
#48 openindiana
#49 retropie
#50 crux
#51 minix
#52 sabayon
#53 galliumos
#54 ubuntu-mate
#55 elementary
#56 mageia
#57 puppylinux
#58 trisquel
#59 ubuntustudio
#60 opensolaris
#61 android-x86
#62 hyperbola
#63 openmandriva
#64 mirbsd
#65 deepin
#66 chakra
#67 ubuntu-budgie
#68 kaosx
#69 clonezilla
#70 parrotsec
#71 aptosid
#72 elive
#73 bodhi
#74 endless
#75 antiX
#76 steamOS
#77 redcorelinux
#78 korora
#79 ZorinOS
#80 knoppix
#81 UltimateEdition
#82 PCLinuxOS
#83 lakka
#84 archbang
#85 slax
#86 nutyx
#87 lxle

Hosted on GitHub Pages — Theme by orderedlist

CoreOS

CoreOS

Rank: #32

Website: https://coreos.com/

IRC:

#coreos on Freenode with 135 users online

Description

Container Linux by CoreOS (formerly CoreOS Linux) is an open-source lightweight operating system based on the Linux kernel and designed for providing infrastructure to clustered deployments, while focusing on automation, ease of application deployment, security, reliability and scalability. As an operating system, Container Linux provides only the minimal functionality required for deploying applications inside software containers, together with built-in mechanisms for service discovery and configuration sharing.

Container Linux shares foundations with Gentoo Linux, 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.

Container Linux provides no package manager as a way for distributing payload applications, requiring instead all applications to run inside their containers. Serving as a single control host, a Container Linux instance uses the underlying operating-system-level virtualization features of the Linux kernel to create and configure multiple containers that perform as isolated Linux systems. That way, resource partitioning between containers is performed through multiple isolated userspace instances, instead of using a hypervisor and providing full-fledged virtual machines. This approach relies on the Linux kernel’s cgroups and namespaces functionalities, which together provide abilities to limit, account and isolate resource usage (CPU, memory, disk I/O, etc.) for the collections of userspace processes.

Initially, Container Linux exclusively used Docker as a component providing an additional layer of abstraction and interface 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. 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 protocol for discovering and retrieving container images. 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, 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) containerization standard, which was announced in June 2015.

Container Linux uses ebuild scripts from Gentoo Linux for automated compilation of its system components, and uses systemd as its primary init system with tight integration between systemd and various Container Linux’s internal mechanisms