[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] Potential Atomic 2 Week Release blockers
- From: Daniel J Walsh <dwalsh redhat com>
- To: Dusty Mabe <dusty dustymabe com>, atomic-devel projectatomic io
- Subject: Re: [atomic-devel] Potential Atomic 2 Week Release blockers
- Date: Fri, 13 Nov 2015 10:07:26 -0500
On 11/13/2015 10:03 AM, Dusty Mabe wrote:
>
>
> On 11/12/2015 05:37 PM, Dusty Mabe wrote:
>>
>>
>> On 11/12/2015 05:17 PM, Michael McGrath wrote:
>>> On Thu, Nov 12, 2015 at 3:53 PM, Amanda Carter <acarter redhat com>
>>> wrote:
>>>> Adding the list. Both questions still open.
>>>>
>>> IMHO https://bugzilla.redhat.com/show_bug.cgi?id=1276775 is a blocker
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1278984 not a blocker if
>>> it can be fixed by the next 2 week release. I'm willing to hear
>>> arguments on this one but I don't know that contacting docker from
>>> within a docker container is a common use case (I know openshift does
>>> this for builds but I don't think many are running openshift on atomic
>>> host today).
>>>
>>>
>>
>> One other use case that takes advantage of this is
>> Atoimcapp/Nulecule. I'm not saying it is a large enough audience at
>> this point to prevent release, but just saying that it exists.
>>
>>
>
> BZ 1275593 is pretty much a dup of 1276775 and more people have
> reporting things that are broken there (i.e. cockpit is broken, etc).
> See comments:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1275593
>
Yes we have a fix that needs to get pushed into docker-1.8.2. Was
hoping to wait for docker-1.9, but that is held up with problems of its own.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]