Subject: Re: [atomic-devel] Storage for system containers
Date: Tue, 25 Apr 2017 09:12:39 -0400
Also rm -rf /var/lib/docker in a
devicemapper world is not a good idea. You end up in a strange
world which could leak devices and resources.
atomic storage reset
Is the preferred way.
On 04/24/2017 11:57 PM, Ben Breard wrote:
The only issue I have with using the same location
is that when troubleshooting, it's fairly common to wipe the
storage pool. I think we'd want users to rm -rf /var/lib/docker
without worrying about removing system containers.
Is this still an issue after the current partition scheme
moves to OverlayFS?
NOTE:
please reply-all when responding to this message
In Fedora Atomic Host if we use system containers as
advertised
we end up using `atomic pull --storage ostree` which by
default
throws images into /var/lib/containers/atomic/. This is on
the
root filesystem which may be undesirable.
Since in Fedora 26 the new version of
container-storage-setup allows
us greater control over a "CONTAINER_ROOT" should we
consider trying
to make sure both ostree storage and docker storage get
placed under
that CONTAINER_ROOT?
The current default [1] is to just mount the CONTAINER_ROOT
on
/var/lib/docker.