http-parser library is not updated anymore and does not support
>> HTTP/2 so it's a dead end anyway
>>
>> Le 8 novembre 2018 10:17:20 GMT+01:00, Olivier Sallou
>> mailto:olivier.sal...@irisa.fr>> a écrit :
>>
>> - Mail original --
ier.sal...@irisa.fr>> À: user@mesos.apache.org
> <mailto:user@mesos.apache.org> Envoyé: Mercredi 7 Novembre
> 2018 12:40:24 Objet: Re: mesos containerizer issue with
> v1.8.0: HTTP response Decoding failed
>
>
>
rg>
Envoyé: Mercredi 7 Novembre 2018 12:40:24
Objet: Re: mesos containerizer issue with v1.8.0: HTTP response Decoding failed
On 11/7/18 11:54 AM, Cecile, Adam wrote:
Hi,
You might be hitting the same bug as I did (no HTTP/2 support in code
pulling images for Mesos).
https://issues.apache.org/
u <
> olivier.sal...@irisa.fr> a écrit :
>>
>>
>>
>> - Mail original -
>>
>>> De: "Olivier Sallou"
>>> À: user@mesos.apache.org
>>> Envoyé: Mercredi 7 Novembre 2018 12:40:24
>>> Objet: Re: mesos container
is not updated anymore and does not support HTTP/2 so
> it's a dead end anyway
>
> Le 8 novembre 2018 10:17:20 GMT+01:00, Olivier Sallou <
> olivier.sal...@irisa.fr> a écrit :
>>
>>
>>
>> - Mail original -
>>
>>> De: "Olivier S
bjet: Re: mesos containerizer issue with v1.8.0: HTTP response Decoding failed
On 11/7/18 11:54 AM, Cecile, Adam wrote:
Hi,
You might be hitting the same bug as I did (no HTTP/2 support in code
pulling images for Mesos).
https://issues.apache.org/jira/browse/MESOS-9364
adding some logs as su
- Mail original -
> De: "Olivier Sallou"
> À: user@mesos.apache.org
> Envoyé: Mercredi 7 Novembre 2018 12:40:24
> Objet: Re: mesos containerizer issue with v1.8.0: HTTP response Decoding
> failed
> On 11/7/18 11:54 AM, Cecile, Adam wrote:
>> Hi,
&
Hi,
Actually I'm wrapping docker client pull request and my server was
running HTTP/2 only.
Check http-parser you may find a hint regarding this "bad" constant.
Regards,
On 11/7/18 12:40 PM, Olivier Sallou wrote:
> On 11/7/18 11:54 AM, Cecile, Adam wrote:
>> Hi,
>>
>> You might be hitting the s
On 11/7/18 11:54 AM, Cecile, Adam wrote:
> Hi,
>
> You might be hitting the same bug as I did (no HTTP/2 support in code
> pulling images for Mesos).
> https://issues.apache.org/jira/browse/MESOS-9364
adding some logs as suggested in your issue, error code is different,
getting "invalid constan
On 11/7/18 11:54 AM, Cecile, Adam wrote:
> Hi,
>
> You might be hitting the same bug as I did (no HTTP/2 support in code
> pulling images for Mesos).
> https://issues.apache.org/jira/browse/MESOS-9364
>
> My report also include some code you can add in C++ code of the fetcher
> to retrieve the
Hi,
You might be hitting the same bug as I did (no HTTP/2 support in code
pulling images for Mesos).
https://issues.apache.org/jira/browse/MESOS-9364
My report also include some code you can add in C++ code of the fetcher
to retrieve the actual message coming from the http response parser libra
On 11/7/18 10:48 AM, Olivier Sallou wrote:
> On 11/7/18 10:38 AM, Olivier Sallou wrote:
>> Hi,
>>
>> I installed mesos from source. It works fine with docker containerizer.
>>
>> Howerver it fails with unified containerizer at container start.
>>
>> It used to work on a previous (older release) in
On 11/7/18 10:38 AM, Olivier Sallou wrote:
> Hi,
>
> I installed mesos from source. It works fine with docker containerizer.
>
> Howerver it fails with unified containerizer at container start.
>
> It used to work on a previous (older release) install. In the meanwhile,
> some system libs etc..
Hi,
I installed mesos from source. It works fine with docker containerizer.
Howerver it fails with unified containerizer at container start.
It used to work on a previous (older release) install. In the meanwhile,
some system libs etc.. have been upgraded.
In logs I have the following:
I1107
14 matches
Mail list logo
