On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe wrote:
>
>
> On 12/12/2016 05:19 PM, Jason Brooks wrote:
>> On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote:
>>>
>>> After I get a bug[1] fixed and out the door I'm going to publish
>>> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
On 12/12/2016 05:41 PM, Jason Brooks wrote:
> On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe wrote:
>>
>>
>> On 12/12/2016 05:19 PM, Jason Brooks wrote:
>>> On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote:
After I get a bug[1] fixed and out the door I'm going to publish
a blog pos
On Mon, Dec 12, 2016 at 2:46 PM, Dusty Mabe wrote:
>
>
> On 12/12/2016 05:41 PM, Jason Brooks wrote:
>> On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe wrote:
>>>
>>>
>>> On 12/12/2016 05:19 PM, Jason Brooks wrote:
On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote:
>
> After I get a bug
On 12/13/2016 01:02 PM, Colin Walters wrote:
> On Tue, Dec 13, 2016, at 12:45 PM, Clayton Coleman wrote:
>> Are the POSIX issues in applications running on overlay mostly resolved now?
>> I.e. if we flipped the default would be reasonably able to support a
>> diverse range of Linux workloads w
Yes I plan on writing a blog on this once we have an update to
docker-storage-setup to handle setting up /var/lib/docker on a separate
partition.
https://github.com/projectatomic/docker-storage-setup/pull/175
Once we get this merged, we could easily move to overlayfs as default on
atomic host, b
On 12/13/2016 02:18 PM, Dusty Mabe wrote:
>
> On 12/13/2016 01:02 PM, Colin Walters wrote:
>> On Tue, Dec 13, 2016, at 12:45 PM, Clayton Coleman wrote:
>>> Are the POSIX issues in applications running on overlay mostly resolved
>>> now? I.e. if we flipped the default would be reasonably able to
On 12/14/2016 07:51 AM, Daniel J Walsh wrote:
>
> I have heard that the issue with yum/rpm is being worked on in the kernel.
> For those that to not know the issue is for programs that open a file twice
> once for readonly and then later for read/write. In the first open the file
> is
> on the
On 12/14/2016 10:38 AM, Dusty Mabe wrote:
>
> On 12/14/2016 07:51 AM, Daniel J Walsh wrote:
>> I have heard that the issue with yum/rpm is being worked on in the kernel.
>> For those that to not know the issue is for programs that open a file twice
>> once for readonly and then later for read/writ
Dan, Dusty, Vivek:
So far nobody has defined (technically) the exact problem with overlayfs
and how it affects applications which want to write data inside the
container.
Note that just saying "don't use Overlay for persistent data" really
isn't good enough. Apps in containers frequently write d
On 12/15/2016 12:18 PM, Josh Berkus wrote:
> Dan, Dusty, Vivek:
>
> So far nobody has defined (technically) the exact problem with overlayfs
> and how it affects applications which want to write data inside the
> container.
>
> Note that just saying "don't use Overlay for persistent data" really
The Docker docs also has a breakdown of incompatibilities:
https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/#/overlayfs-compatibility
Notably, there's the open(2) issue that has already been
mentioned. The second issue is that rename(2) can fail if
trying to move a dir acro
On 12/16/2016 03:16 AM, Marius Vollmer wrote:
> Vivek Goyal writes:
>
>> [...] And if overlayfs does not work for a user, switching back to
>> devmapper should be easy.
>>
>> - atomic storage reset
>> - edit /etc/sysconfig/docker-storage-setup and set
>> STORAGE_DRIVER=devicemapper
>> - restar
12 matches
Mail list logo
