Iain - I’ve seen this same behavior. I’ve not found a work-around, though would agree that it would be a “nice to have” feature. > On Mar 26, 2024, at 7:22 AM, Iain Stott <Iain.Stott@xxxxxxx> wrote: > > Hi, > > We are trying to deploy Ceph Reef 18.2.1 using cephadm on mixed architecture hosts using x86_64 for the mons and aarch64 for the OSDs. > > During deployment we use the following config for the bootstrap process, where $REPOSITORY is our docker repo. > > [global] > container_image = $REPOSITORY/ceph/ceph:v18.2.1 > [mgr] > mgr/cephadm/container_image_base = $REPOSITORY/ceph/ceph:v18.2.1 > mgr/cephadm/container_image_prometheus = $REPOSITORY/ceph/prometheus:v2.33.4 > mgr/cephadm/container_image_node_exporter = $REPOSITORY/ceph/node-exporter:v1.3.1 > mgr/cephadm/container_image_grafana = $REPOSITORY/ceph/ceph-grafana:8.3.5 > mgr/cephadm/container_image_alertmanager = $REPOSITORY/ceph/alertmanager:v0.23.0 > [osd] > container_image = $REPOSITORY/ceph/ceph:v18.2.1 > Once the bootstrap process is complete, if we do a ceph config dump, the container image for global and osd changes from version tag to sha reference, meaning that when deploying the containers on the OSDs they try using the amd64 container image and not the aarch64 image and fail deployment. > > Is there a config setting we are missing or a workaround for this? > > Thanks > Iain > > Iain Stott > OpenStack Engineer > Iain.Stott@xxxxxxx > [THG Ingenuity Logo]<https://www.thg.com> > www.thg.com<https://www.thg.com/> > [LinkedIn]<https://www.linkedin.com/company/thgplc/?originalSubdomain=uk> [Instagram] <https://www.instagram.com/thg> [X] <https://twitter.com/thgplc?lang=en> > _______________________________________________ > 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
 |