Potential issues with the latest Ignite Docker image

[dmagda]

Igniters,

One of our users reported an issue related to the latest docker image:

https://twitter.com/jarbot/status/1245945256756957184?s=21

Can someone check what exactly was broken?

Denis


--
-
Denis

[Jared Gholston]

I'm not exactly sure what version of the ignite docker image we are using,
but it is not using BusyBox.  The new version the following fails:

wget https://google.com

this works:

wget http://google.com


Any https wget fails on the new docker image.  We import several jars using
the EXTERNAL_LIBS configuration. The libs are coming from s3 and maven
central all of which require https.

I hope that helps,
Jared




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[dmagda]

Jared, thanks for the details.

Igniters, is there anyone who had a chance prepared our Docker images for
releases can look into the reported issue?

-
Denis


On Fri, Apr 3, 2020 at 2:45 PM Jared Gholston <[hidden email]> wrote:

> I'm not exactly sure what version of the ignite docker image we are using,
> but it is not using BusyBox.  The new version the following fails:
>
> wget https://google.com
>
> this works:
>
> wget http://google.com
>
>
> Any https wget fails on the new docker image.  We import several jars using
> the EXTERNAL_LIBS configuration. The libs are coming from s3 and maven
> central all of which require https.
>
> I hope that helps,
> Jared
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[vveider]

Do you see the error?
Is it telling about missing or wrong certificate or something else?

> On 8 Apr 2020, at 02:18, Denis Magda <[hidden email]> wrote:
>
> Jared, thanks for the details.
>
> Igniters, is there anyone who had a chance prepared our Docker images for
> releases can look into the reported issue?
>
> -
> Denis
>
>
> On Fri, Apr 3, 2020 at 2:45 PM Jared Gholston <[hidden email]> wrote:
>
>> I'm not exactly sure what version of the ignite docker image we are using,
>> but it is not using BusyBox.  The new version the following fails:
>>
>> wget https://google.com
>>
>> this works:
>>
>> wget http://google.com
>>
>>
>> Any https wget fails on the new docker image.  We import several jars using
>> the EXTERNAL_LIBS configuration. The libs are coming from s3 and maven
>> central all of which require https.
>>
>> I hope that helps,
>> Jared
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>