It’s great to see the CoreOS community evolving like this! How can I get involved?
Thanks to dustymabe, I’m playing around with building custom atomic images but I’ve run into quite a few problems. Most of it has to do with fedora philosophy: we like python. Yum, dnf, the atomic toolset, cloud-init (not fedora specific but standard server init). CoreOS is bringing a lot of low level tooling to the table and I’ve seen dustymabe start some dracut modules for ignition so it’ll replace cloud-init with the rpm-ostree toolchain. How do the CoreOS and Fedora philosophies work together? It seems like the two will be at odds concerning interpreted languages.
With such a fast paced environment, most of the documentation over at project atomic is out of date referencing tpm-ostree-toolbox while fedora atomic will perform builds using its spiritual successor pungi which is a similar wrapper around lorax, rpm-ostree, and other containerized tools. This makes it difficult to catch up to where the atomic project is presently. I would really like to contribute more since I have a vested interest in this project as a modular alternative to CoreOS. Working with the old SDK sometimes felt clunky when installing new modules.
I do have one small contribution over at https://src.fedoraproject.org/rpms/container-selinux/pull-request/1. Anything with RunC as a dependency or docker/rkt/cri-o selinux policies require this package. However, it references a policycoreutil-python as a hard depend. However, %post does not use any python utilities. This seems like it should be a weak or forward depend. After compiling this rpm in a local repo, my fedora atomic builds without any python2,3 or perl dependencies.
As a footnote, dnf repoquery does not respect repo priorities, repo excludes, or rpm versions when compiling a dependency tree. Commands such as dnf repoquery runc --tree --requires or dnf repoquery runc --requires --recursive --resolve will locate dependencies from the same repo the initial package is found at. This bug at least means that building analytical tools for coreos fedora atomic will require some custom tooling.