The error occurs when trying to run an Octopus monitor container on Rocky ( sorry I wasn’t specific ), oddly the mgr container worked fine and it appears to use the same container.
On mesosphere, it ended up being the version of docker I had preloaded on the agent nodes. I ended up blowing them away and letting mesosphere deploy docker from its bootstrap container. I usually build nodes using ansible and I had docker in my general script. Early mesosphere was a bit whiney but they got much better quickly once they released the community version and took feedback. -Brent -----Original Message----- From: Marc <m...@f1-outsourcing.eu> Sent: Monday, August 8, 2022 4:10 AM To: Brent Kennedy <bkenn...@cfl.rr.com>; ceph-users@ceph.io Subject: RE: [ceph-users] Re: Upgrade paths beyond octopus on Centos7 > When the containers start on podman 4, they show an error regarding > groups. > Searching on the web for that error only returns posts saying you can > ignore it, but the container/service wont start. I thought upgrading > to quincy I just did a pull from centos 9 stream, and this runs fine podman run -it -v /dev/log:/dev/log --network host ceph/ceph:v17 /bin/bash Imho, then you should be able to correct anything that is wrong, not? > > This podman issue basically shows the flaw in the thinking that > containers solve the OS issue( I ran into this with Docker and > mesosphere, so I kinda If I may ask, what was it with mesos? _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
