# Repeated trouble download Docker image

**URL:** <https://www.rubin.community/t/repeated-trouble-download-docker-image/2783>\
**Category:** Support\
**Tags:** docker\
**Created:** [March 23, 2018, 3:58pm UTC](https://www.rubin.community/t/repeated-trouble-download-docker-image/2783 "2018-03-23T15:58:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![josh](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/josh/32/72_2.png) [@josh](https://www.rubin.community/u/josh)\
**Post date:** [March 23, 2018, 4:37pm UTC](https://www.rubin.community/t/repeated-trouble-download-docker-image/2783/4 "2018-03-23T16:37:12Z")

</div>

I have not personally seen errors extracting docker layers. Possibly explanations are:

- the data being returned from docker hub is corrupt. This seems unlikely.
- the data is being corrupted in transmission. While I have seen byte swapping errors make it past the tcp header checksum (and the fits header checksum at the same time…), docker hub transfers are (always?) over https, so there would be robust tls hashes as well. It is possible to offload some parts of tls processing to the nic – I don’t know if this is done on osx.
- software bugs involving tls processing or within docker – as @brianv0 can’t reproduce with the same docker version, this also seems unlikely.
- os (kernel) bugs
- cpu/cpu cache corruption
- bus (pcie/sata/etc.) transfer corruption
- memory corruption
- disk corruption

---

_[View the full topic](https://www.rubin.community/t/repeated-trouble-download-docker-image/2783)._
