Fedora CoreOS Sees Its First Preview Release

[phoronix]

Phoronix: Fedora CoreOS Sees Its First Preview Release

It was a year and a half ago that Red Hat acquired CoreOS while today they are announcing their first preview release of Fedora CoreOS...

http://www.phoronix.com/scan.php?page=news_item&px=Fedora-CoreOS-Preview

[horizonbrave]

uh oh,
what's the difference with Silverblue?
which one is more similar to Proxmox?

[busukxuan]

uh oh,
what's the difference with Silverblue?
which one is more similar to Proxmox?

If I understand correctly this one is all about running containers, probably in the cloud; Silverblue is more of a redo of the existing OS structure, with application software being installed mainly as Flatpak packages, which does involve container technology, but as a means rather than the goal.

[ChamPro]

uh oh,
what's the difference with Silverblue?
which one is more similar to Proxmox?

CoreOS - oriented toward minimal installs on servers on-premise or in the cloud to run applications (mostly in containers), OS updates are done atomically
Silverblue - a developer desktop built on top of the CoreOS idea where most installs are done through other package managers than yum (flatpak, npm, etc.)

Proxmox - medium weight server OS for hosting KVM and LXC based workloads
Fedora server (and RHEL 8, eventually CentOS 8) are probably the closest to Proxmox, especially with the now more complete web front-ends to manage the server (a feature called Cockpit)

[Guest]

Telemetry in production sure sounds like a good idea. I assume it will add up to wasted CPU cycles, because the firewall will be set to drop these telemetry requests.

[starshipeleven]

uh oh,
what's the difference with Silverblue?
which one is more similar to Proxmox?

Proxmox is mostly about KVM, full virtualization, these are about containers.

[starshipeleven]

Telemetry in production sure sounds like a good idea. I assume it will add up to wasted CPU cycles, because the firewall will be set to drop these telemetry requests.

It's safe to assume that people running a server OS designed around containers are capable of RTFM and disabling this service if they don't want it https://github.com/coreos/fedora-coreos-pinger/

or maybe even do the unthinkable, uninstall the whole package.

This isn't fucking Windows, man.

[Guest]

It's safe to assume that people running a server OS designed around containers are capable of RTFM and disabling this service if they don't want it https://github.com/coreos/fedora-coreos-pinger/

or maybe even do the unthinkable, uninstall the whole package.

This isn't fucking Windows, man.

Have you read my post? I've posted about the fact that this distro will probably run in containers behind a firewall, which will probably be set up to not allow telemetry through even if someone forgets to disable it.

[starshipeleven]

Have you read my post? I've posted about the fact that this distro will probably run in containers behind a firewall, which will probably be set up to not allow telemetry through even if someone forgets to disable it.

Have you read the article? It's clearly stated that this is a distro designed to a host to run containers.

Why would someone run a container host distro in a container?
Why are you placing anything resembling a distro in a container at all anyway?
It's not a VM, nor a chroot. You usually have only a single application and its libraries in a container.

[re:fi.64]

uh oh,
what's the difference with Silverblue?
which one is more similar to Proxmox?

Silverblue and CoreOS share quite a bit of technology (e.g. rpm-ostree) and ideology, but there are some major differences. Silverblue is designed for home / workstation use. The base image comes with Flatpak already set up, a full GNOME installation, etc. In a default install, you have podman for managing containers, which is like Docker but daemon-less and with a rootless mode.

CoreOS, on the other hand, is designed to be a host operating system for running containers on servers. The base image here is far more stark and minimal, and it also comes with Ignition which can be used to quickly configure large amounts of node servers. In addition, it contains multiple container runtimes out-of-the-box, adding Docker and CRI-O in addition to podman.

They do share the base concepts, such as ostree / rpm-ostree, the immutable rootfs, and atomic upgrades. Of course, you can still install normal rpms on both via rpm-ostree as well.