Telemetry connection issues with >=0.2.1

[chevdor]

I used to be able to connect to telemetry without any problem.
I started noticing issues since 0.2.1. The issue is still in 0.2.2.

logs

2018-08-01 15:22:30 Parity ·:· Polkadot
2018-08-01 15:22:30   version 0.2.2-c8a4adfd-x86_64-linux-gnu
2018-08-01 15:22:30   by Parity Technologies, 2017, 2018
2018-08-01 15:22:30 Chain specification: Krumme Lanke
2018-08-01 15:22:30 Node name: One Cool
2018-08-01 15:22:30 Roles: FULL
2018-08-01 15:22:31 Best block: #903079
2018-08-01 15:22:31 Local node address is: /ip4/0.0.0.0/tcp/30333/p2p/QmeVye9...z8nByZP3ve
2018-08-01 15:22:31 Idle (0 peers), best: #903079 (e533…5711)
2018-08-01 15:22:31 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:32 New external node address: /ip4/104.40.204.9/tcp/30333/p2p/QmeV...nByZP3ve
2018-08-01 15:22:32 Node PeerId(QmW...XGWG7) with peer ID 3 through protocol [100, 111, 116] disconnected
2018-08-01 15:22:32 Node PeerId(QmY3...ay4HvAB) with peer ID 2 through protocol [100, 111, 116] disconnected
2018-08-01 15:22:32 Node PeerId(QmW...2P9fGn) with peer ID 1 through protocol [100, 111, 116] disconnected
2018-08-01 15:22:33 Node PeerId(QmR...VSTChmrd) with peer ID 0 through protocol [100, 111, 116] disconnected
2018-08-01 15:22:33 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:33 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:34 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:35 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:35 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:35 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:35 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:35 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:36 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:36 Connection dropped unexpectedly. Reconnecting to telemetry server...
2018-08-01 15:22:36 Syncing, target=#903444 (1 peers), best: #903383 (4ecf…d0f8)

[chevdor]

I do NOT see the issue for instance using 0.3.0-9d7a3c1-x86_64-linux-gnu.

[chevdor]

I should have mentioned I see the issue using the docker image and 0.2.1-0.2.2 may match the time where I switched to using a 2 stage image using ubuntu as base for the second. See #463

[chevdor]

Closing this one as I successfully built an image with 0.2.2 that connects without issue to telemetry. This issue is a docker issue, not an issue with polkadot itself. See #463

[chevdor]

I tested various images and it seems to be related to the ca-certificates in /usr/share.
Having them (baseimage) it works, not having them (ubuntu) it fails.