Re: Why you might want packages not containers for Ceph deployments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 22, 2021 at 11:58 AM Martin Verges <martin.verges@xxxxxxxx> wrote:
>
> > There is no "should be", there is no one answer to that, other than 42.
> Containers have been there before Docker, but Docker made them popular,
> exactly for the same reason as why Ceph wants to use them: ship a known
> good version (CI tests) of the software with all dependencies, that can be
> run "as is" on any supported platform.
>
> So ship it tested for container software XXX and run it on YYY. How will
> that benefit me as a user? There are differences when running a docker
> container, lxc, nspawn, podman, kubernetes and whatever. So you trade error
> A for error B. There are even problems with containers if you don't use
> version X from docker. That's what the past told us, why should it be
> better in the future with even more container environments. Have you tried
> running rancher on debian in the past? It breaks apart due to iptables or
> other stuff.

Rook is based on kubernetes, and cephadm on podman or docker.  These
are well-defined runtimes.  Yes, some have bugs, but our experience so
far has been a big improvement over the complexity of managing package
dependencies across even just a handful of distros.  (Podman has been
the only real culprit here, tbh, but I give them a partial pass as the
tool is relatively new.)
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux