Vivek Goyal writes:
> On Fri, Apr 15, 2016 at 03:53:20PM +0300, Marius Vollmer wrote:
>
> - Status of current configuration
> - Reset the configuration.
> - Help users move from loop devices to proper block devices
> - Help user tear town existing thin pool and setup a fresh one.
>
>
Vivek Goyal writes:
> On Fri, Apr 15, 2016 at 03:53:20PM +0300, Marius Vollmer wrote:
>
>> We need two operations:
>>
>> - Take a block device and use it for storing Docker images and
>>containers.
>>
>> - Reset the docker storage setup so that block devices that were
>>previously used
On Fri, Apr 15, 2016 at 03:53:20PM +0300, Marius Vollmer wrote:
> Hi,
>
> I am working on this, as you know:
>
> https://github.com/cockpit-project/cockpit/wiki/Atomic:-Docker-Storage
>
> and after getting my misunderstandings of docker-storage-setup cleared
> up, my next idea is to change t
Daniel J Walsh writes:
>> Thoughts?
>
> I am fine with this, but I would like to try to keep this container
> platform agnostic if at all possible.
Roger.
On 04/15/2016 08:53 AM, Marius Vollmer wrote:
Hi,
I am working on this, as you know:
https://github.com/cockpit-project/cockpit/wiki/Atomic:-Docker-Storage
and after getting my misunderstandings of docker-storage-setup cleared
up, my next idea is to change the "atomic" command to pretty
Kubernetes in some cases will be directly reading the info from the
filesystem/kernel and summarizing that up to the control plane, so
possibly less useful to do the fsnotify work when atomic is a Kube
node. However, definitely may have value in other atomic use cases.
> On Apr 15, 2016, at 8:53
Hi,
I am working on this, as you know:
https://github.com/cockpit-project/cockpit/wiki/Atomic:-Docker-Storage
and after getting my misunderstandings of docker-storage-setup cleared
up, my next idea is to change the "atomic" command to pretty directly
support those use cases.
We need two op
