Error downloading image

Product support
1

I am having trouble Using resin.io at my home that is served only by DSL. When I try to update or deploy new devices, the image downloads keep timing out. I fear the worst but if anyone knows of a network setting or what ever that info would be of interest.

Would local deployment, since that is an option, be the way to go here?

22.08.18 00:12:22 (-0700) Removing network 'default'
22.08.18 00:12:22 (-0700) Creating network 'default'
22.08.18 00:12:22 (-0700) Creating volume 'resin-data'
22.08.18 00:12:23 (-0700) Downloading image 'registry2.resin.io/v2/3d57ab6f85956c3b55df48aa1c7f318e@sha256:e07a21448210950f5621d9d129e8ea2255f6847e7203e00ef70c27ce5bcaa23c'
22.08.18 00:20:38 (-0700) Failed to download image 'registry2.resin.io/v2/3d57ab6f85956c3b55df48aa1c7f318e@sha256:e07a21448210950f5621d9d129e8ea2255f6847e7203e00ef70c27ce5bcaa23c' due to 'could not get decompression stream: Get https://resin-production-registry2-cloudformation.s3.amazonaws.com/prod/docker/registry/v2/blobs/sha256/6a/6afcd6297637f28c2262def24fd3ac29684b1b2eecfbde94a3bbdcec6be86dd5/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIPVZA7LDCHZ6P54A%2F20180822%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180822T072028Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=e9099ef76cd7ef5417c360daf47c1c021c60d99e5cf66c63823d52e4dd71de8c: net/http: TLS handshake timeout'
22.08.18 00:20:43 (-0700) Downloading image 'registry2.resin.io/v2/3d57ab6f85956c3b55df48aa1c7f318e@sha256:e07a21448210950f5621d9d129e8ea2255f6847e7203e00ef70c27ce5bcaa23c'
4

No Longer an issue

5

Anything you could share that would benefit future audiences of this thread?

7

Yes apologies, for the slow follow up.

Unfortunately I could not get a conclusive resolution, but I can share none the less. I was working with resinoS Resin OS 2.13.6+rev1 and was having the issue described. When I dropped back to Resin OS 2.12.7+rev1 I was able to download images more reliably. Now with Resin OS 2.15.1+rev2 everything is more stable so my thinking is that the issue has resolved due to some change in the resin.io backend and not as a result of the resinOS version.

If you have any questions please feel free to PM me.

cheers.