On 04/28/2017 01:09 PM, Giuseppe Scrivano wrote:
Hi,
Dusty Mabe writes:
i'm going to show how little I know with this question, but would it be possible
to have a separate partition for system containers that was essentially xfs + an
overlayfs of the host filesystem?
On 04/27/2017 08:51 AM, Daniel Walsh wrote:
> On 04/27/2017 06:44 AM, Giuseppe Scrivano wrote:
>> Mounting a partition at /var wouldn't work with system containers.
>>
>> System containers are stored in the OSTree storage and on Atomic Host
>> they are checked out to
On 04/25/2017 12:08 PM, Dusty Mabe wrote:
>
>
> On 04/25/2017 08:25 AM, Daniel Walsh wrote:
>> On 04/24/2017 01:56 PM, Dusty Mabe wrote:
>> Perhaps we should just mount a partition at /var or move /var/lib/docker
>> to /var/lib/containers/docker and make a symbolic link from
>>
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
If we move the link under /var/lib/containers/docker then removing this
would not affect /var/lib/containers/ostree or /var/lib/containers/storage
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
On 04/24/2017 01:56 PM, Dusty Mabe 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