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?
On Mon, Apr 24, 2017 at 12:56 PM, Dusty Mabe <du...@dustymabe.com
<mailto:du...@dustymabe.com>> wrote:
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.
Dusty
[1]
https://src.fedoraproject.org/cgit/rpms/docker.git/tree/docker.spec?h=f26#n535
<https://src.fedoraproject.org/cgit/rpms/docker.git/tree/docker.spec?h=f26#n535>
--
Ben Breard
Sr Technology Product Manager - Linux Containers
Mobile: 972-816-9081
