Ah. Makes sense. Might be nice if the container build appended something like "cephadm container" to the redhat-release string, though. A more concerning item is that the container is based on CentOS 8 Stream. I'd feel more comfortable if the base OS was more release- oriented. Especially since Centos8 Stream EOL'ed back around May. More importantly, the Ceph archives for CentOS 8 went down the Memory Hole. That's really worrisome. Makes it questionable that it would be easy to build from source on a blank system now. Yanking repos is not the Linux Way. I could probably spin up a copy of CentOS 2, because repos are still online even if no sensible person would want it for a production server. But not so the CentOS 8 enterprise extensions. They;re gone. On Fri, 2024-07-19 at 09:00 +0200, Robert Sander wrote: > On 7/18/24 21:50, Tim Holloway wrote: > > I've been setting up a cookbook OSD creation process and as I > > walked > > through the various stages, I noted that the /etc/redhat-release > > file > > said "CentOS Stream 8". > > This is the case because the orachestrator cephadm uses container > images > based on CentOS 8. > > When you execute "cephadm shell" it starts a container with that > image > for you. > > Regards > -- > Robert Sander > Heinlein Consulting GmbH > Schwedter Str. 8/9b, 10119 Berlin > > https://www.heinlein-support.de > > Tel: 030 / 405051-43 > Fax: 030 / 405051-19 > > Amtsgericht Berlin-Charlottenburg - HRB 220009 B > Geschäftsführer: Peer Heinlein - Sitz: Berlin > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |