[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[atomic-devel] Thinking about CRI-O and Docker on Atomic Host
- From: Colin Walters <walters verbum org>
- To: atomic-devel projectatomic io
- Subject: [atomic-devel] Thinking about CRI-O and Docker on Atomic Host
- Date: Thu, 01 Jun 2017 11:58:31 -0400
I've seen some interesting work on CRI-O for Kube/OpenShift. But
I'm wondering about what people are thinking the future of
docker.service and /usr/bin/docker is (particularly for Atomic Host).
The particular intersection with AH is handling container storage;
AIUI right now you can't have CRI-O and Docker share the same
storage pool.
So...should a CRI-O installer `systemctl stop docker.service; systemctl mask docker.service`
and reuse the partition we've set up for /var/lib/docker? Or do we
expect people to set up a separate partition?
(It feels like the answer is probably "both")
Perhaps in the big picture for the single-node case we point people
at `oc cluster up` etc? (Which itself should be a system container probably
to avoid the obvious bootstrapping problem?)
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]