Ah - so the atomic image is not just a centos respin with a slight leaning towards running docker .... I stand corrected and will spend some hours with Atomic docs before asking more stupid questions. Thanks for the quick reply. regards, Bent On 9 January 2016 at 09:48, Vincent Van der Kussen <vincent at vanderkussen.org > wrote: > On 2016-01-09 06:50, Bent Terp wrote: > > Hi, > > this may be a deliberate choice but I can't really figure out why one > would make that decision... > > [centos at atomic ~]$ sudo yum update > sudo: yum: command not found > [centos at atomic ~]$ rpm -ql yum | grep bin > /usr/bin/yum > [centos at atomic ~]$ ls -l /usr/bin/yum > ls: cannot access /usr/bin/yum: No such file or directory > [centos at atomic ~]$ > > I used the latest > http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-GenericCloud.qcow2 > in an RDO deploy. I don't experience the same issue with the regular image > only with the Atomic. > > regards, > Bent > > > Hi Ben, > > This is normal. Atomic uses rpm-ostree[1] to bring in all the updates at > once. > > Regards, > Vincent > > [1] http://www.projectatomic.io/docs/os-updates/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20160109/cd080191/attachment-0008.html>