strigazi added a new comment to an issue you are following:
``
We use atomic hosts in two different ways in production and our users follow two different
usage patterns.
1. as a kubernetes container runtime
2. swarm cluster or standalone docker host
Pattern A
The user has short living clusters (of atomic hosts) and recreates often (compute
intensive workloads) [These users expect to have the latest stable version when they
create a new cluster and they don't necessarily care about upgrading. However,
upgrading is a nice-to-have feature for them.]
Pattern B
The user has long running clusters for production services [these users want a relatively
new version of docker (6 months old), upgrading is very important for them]
As service provider who offer atomic hosts I would be happy with running the runtimes in
system containers. So +1 on all arguments in favor. Regarding the arguments against: Two
steps to install a container runtime is reasonable. I think the space load is compensated
by having more options and I don't think it is a big problem for usage on
public/private clouds. The last two can be tricky but are also giving flexibility. However
it would be nice to be able to select the version of the runtime eg atomic install
cri-o:1.x or atomic install docker:17.09 even a newer release is available. It is more
clear what you get instead of atomic install docker:latest.
Finally, having a docke-ce system container would be really nice to have.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/360