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

Re: [atomic-devel] Thinking about CRI-O and Docker on Atomic Host

On Jun 1, 2017 17:58, "Colin Walters" <walters verbum org> wrote:
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")

CRI-O can't actually use the Docker storage transparently. Either you use skopeo to copy images from Docker to cri-o storage or you start from scratch. 

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]