I'm using NixOS happily since 2014 after getting messed up in pacman dependencies on Arch and haven't looked back. But their too radical shift from LSB makes for a less attractive enterprise story. Hopefully GuixSD[1] can plug that hole due to the GNU brand as it has been progressing nicely.
We've also built https://github.com/vpsfreecz/vpsadminos recently which is based on not-os / NixOS
Also Atomic is more than just an OS; it's a system of reliable upgrades / versions switching. So it's got something in common with NixOS.
I used to be a gnome foundation member (I trained Andrea Veri on the sysadmin team who trained Patrick Uiterwijk, the current lead sysadmin for GNOME) when Colin Watson wrote OSTree. He was talking about it and some of the ideas from it at the KDE/GNOME desktop summit in Berlin (2011ish) in some of the comments after https://desktopsummit.org/program/sessions/improving-how-we-...
At the following Boston (GNOME) developer summit one of the big conversational points sans Ubuntu pulling away from GNOME to build Unity was the idea of GNOME OS because Linux was hard then. He built rpm-ostree after that, and it was after CoreOS as a distro was a thing.
rpm-ostree's first commit was Dec 21, 2013: https://github.com/projectatomic/rpm-ostree/commit/958dfa435...
https://coreos.com/blog/coreos-fourth-birthday CoreOS as a company was created on July 13th, 2013.
TL;DNR: It's complicated, but Atomic as a distro most definitely does not predate ContainerLinux as rpm-ostree didn't exist when CoreOS the company was founded.
Forgive me for poking around a little more but I like reading computer history. That rpm-ostree first commit was an import from something called pkgsys-ostree. The first commit in pkgsys-ostree was only a little earlier; Aug 2013.
[1]: https://nixos.org/nix/ [2]: https://ostree.readthedocs.io/
CoreOS = 2013 Atomic host = 2014
But Atomic was architected as containers infrastructure and is/was a direct competitor to CoreOS and other lightweight container OSes.
People in the desktop team had been working on read-only root OS's for a long time, and it was only at a certain point that RH management bought off on forming a product/spin. But to say that work only started once Atomic was a thing would be inaccurate.
It's probably fair to say that ChromeOS/CoreOS lit a match under some upper management though.