7 ms·

Fedora CoreOS seems like it has some pretty significant restrictions > It does not yet include native support for Azure, DigitalOcean, GCE, Vagrant, or the

by zymhan 7y ago

Fedora CoreOS seems like it has some pretty significant restrictions > It does not yet include native support for Azure, DigitalOcean, GCE, Vagrant, or the Container Linux community-supported platforms. > The rkt container runtime is not included. > Fedora CoreOS provides best-effort stability, and may occasionally include regressions or breaking changes for some use cases or workloads.

wmf 7y ago
This is the Red Hat "stay in business" business model, not the CoreOS "make it up in volume" business model.
- bdutta 7y ago
  Or IBM
- mixmastamyk 7y ago
  How is breaking compat good for business?
newnewpdro 7y ago
>> The rkt container runtime is not included. rkt is dead
- c0restraint 7y ago
  It is? The GitHub project page does not indicate that: https://github.com/rkt/rkt/ https://github.com/rkt/rkt/
  - wmf 7y ago
    It's really dead. rkt never got much adoption and now Red Hat is promoting Podman instead.
    - stingraycharles 7y ago
      But Podman is not the same thing at all. Oh well. I always liked rkt, mostly as a sane alternative to Docker’s client/server and security model. What’s the best alternative nowadays ?
      - plapetomain 7y ago
        systemd nspawn
        pkulak 7y ago
        Wow, I'd never heard of that. I've been using LXD for a while now and love it. From a quick glance at the docs, I'm not sure what benefits this has, apart from not requiring Snap. :D
        newnewpdro 7y ago
        If you're on a systemd distro, one advantage is you already have systemd-nspawn. Although, on debian boxes, it's split out into the systemd-container package. Another advantage is it's somewhat integrated into the rest of systemd, having hooks into systemd-machined and the machinectl tooling, and an out-of-box instance unit file for systemd-nspawn@ where the instance name maps to the machine name. Meaning you can trivially start a container w/`systemctl start systemd-nspawn@that-contained-webservice` having nothing more than something useful in /var/lib/machines/that-contained-webservice/, or enable it to start at boot like any other systemd service i.e. `systemctl enable systemd-nspawn@that-contained-webservice`. BTW, rkt was basically just a wrapper around systemd-nspawn, though the pluggable stages supported alternative containment mechanisms. The nspawn stage1 is what was originally shipped from the beginning.
        gigatexal 7y ago
        Won’t be long until we do systemd ls... I jest but systemd really is taking over a lot of functionality
  - kitotik 7y ago
    Seems it’s at least trending towards dead. Hashicorp Nomad recently deprecated the rkt driver for lack of adoption.
    - schmichael 7y ago
      As noted elsewhere in the thread: indeed rkt is dead. https://github.com/pascomnet/nomad-driver-podman https://github.com/pascomnet/nomad-driver-podman is a WIP Podman driver. We're discussing creating our own containerd-based driver, but there's no plans yet.
  - chipsa 7y ago
    Last release was 2 years ago. It's either dead or feature complete and bug free.
  - thebeardisred 7y ago
    It was donated to the CNCF years ago. As of today, it's the only "Archived" CNCF project: https://www.cncf.io/archived-projects/ https://www.cncf.io/archived-projects/ (https://web.archive.org/web/20200205190817/https://www.cncf.io/archived-projects/ https://web.archive.org/web/20200205190817/https://www.cncf....)
  - fcantournet 7y ago
    It is 100% we're finishing our migration away from it right now. Never getting kubernetes support killed it.
  - blixtra 7y ago
    A former rkt dev here. rkt was archived by the CNCF with our blessings. Was just speaking to other rkt folks at FOSDEM about archiving the project on GH as well, which should happen shortly. We will also announce deprecation of rkt in Flatcar Container Linux very soon. rkt really changed the container runtime landscape for the best and we're happy to see that other projects improved because if it and that the space was able to consolidate a bit.
    - deleted 7y ago
      [deleted]
kashyapc 7y ago
[I work at Red Hat, but not related to CoreOS.] A small nit-pick: Not having Vagrant is not a "significant restriction". FWIW, there is the robust and well-documented virt-builder[1] tool that plays well with KVM, Xen and other stacks. (Related documentation here[2] -- replace "f27" with the latest Fedora release.) [1] http://libguestfs.org/virt-builder.1.html http://libguestfs.org/virt-builder.1.html [2] https://developer.fedoraproject.org/tools/virt-builder/about.html https://developer.fedoraproject.org/tools/virt-builder/about...

by zymhan 7y ago

wmf 7y ago

This is the Red Hat "stay in business" business model, not the CoreOS "make it up in volume" business model.

bdutta 7y ago
Or IBM
mixmastamyk 7y ago
How is breaking compat good for business?

newnewpdro 7y ago

>> The rkt container runtime is not included. rkt is dead

c0restraint 7y ago
It is? The GitHub project page does not indicate that: https://github.com/rkt/rkt/ https://github.com/rkt/rkt/
- wmf 7y ago
  It's really dead. rkt never got much adoption and now Red Hat is promoting Podman instead.
  - stingraycharles 7y ago
    But Podman is not the same thing at all. Oh well. I always liked rkt, mostly as a sane alternative to Docker’s client/server and security model. What’s the best alternative nowadays ?
    - plapetomain 7y ago
      systemd nspawn
      - pkulak 7y ago
        Wow, I'd never heard of that. I've been using LXD for a while now and love it. From a quick glance at the docs, I'm not sure what benefits this has, apart from not requiring Snap. :D
        newnewpdro 7y ago
        If you're on a systemd distro, one advantage is you already have systemd-nspawn. Although, on debian boxes, it's split out into the systemd-container package. Another advantage is it's somewhat integrated into the rest of systemd, having hooks into systemd-machined and the machinectl tooling, and an out-of-box instance unit file for systemd-nspawn@ where the instance name maps to the machine name. Meaning you can trivially start a container w/`systemctl start systemd-nspawn@that-contained-webservice` having nothing more than something useful in /var/lib/machines/that-contained-webservice/, or enable it to start at boot like any other systemd service i.e. `systemctl enable systemd-nspawn@that-contained-webservice`. BTW, rkt was basically just a wrapper around systemd-nspawn, though the pluggable stages supported alternative containment mechanisms. The nspawn stage1 is what was originally shipped from the beginning.
        gigatexal 7y ago
        Won’t be long until we do systemd ls... I jest but systemd really is taking over a lot of functionality
- kitotik 7y ago
  Seems it’s at least trending towards dead. Hashicorp Nomad recently deprecated the rkt driver for lack of adoption.
  - schmichael 7y ago
    As noted elsewhere in the thread: indeed rkt is dead. https://github.com/pascomnet/nomad-driver-podman https://github.com/pascomnet/nomad-driver-podman is a WIP Podman driver. We're discussing creating our own containerd-based driver, but there's no plans yet.
- chipsa 7y ago
  Last release was 2 years ago. It's either dead or feature complete and bug free.
- thebeardisred 7y ago
  It was donated to the CNCF years ago. As of today, it's the only "Archived" CNCF project: https://www.cncf.io/archived-projects/ https://www.cncf.io/archived-projects/ (https://web.archive.org/web/20200205190817/https://www.cncf.io/archived-projects/ https://web.archive.org/web/20200205190817/https://www.cncf....)
- fcantournet 7y ago
  It is 100% we're finishing our migration away from it right now. Never getting kubernetes support killed it.
- blixtra 7y ago
  A former rkt dev here. rkt was archived by the CNCF with our blessings. Was just speaking to other rkt folks at FOSDEM about archiving the project on GH as well, which should happen shortly. We will also announce deprecation of rkt in Flatcar Container Linux very soon. rkt really changed the container runtime landscape for the best and we're happy to see that other projects improved because if it and that the space was able to consolidate a bit.
  - deleted 7y ago
    [deleted]

kashyapc 7y ago

[I work at Red Hat, but not related to CoreOS.] A small nit-pick: Not having Vagrant is not a "significant restriction". FWIW, there is the robust and well-documented virt-builder[1] tool that plays well with KVM, Xen and other stacks. (Related documentation here[2] -- replace "f27" with the latest Fedora release.) [1] http://libguestfs.org/virt-builder.1.html http://libguestfs.org/virt-builder.1.html [2] https://developer.fedoraproject.org/tools/virt-builder/about.html https://developer.fedoraproject.org/tools/virt-builder/about...