# ERROR: Get https://registry-1.docker.io/v2/

**URL:** https://community.xibo.org.uk/t/error-get-https-registry-1-docker-io-v2/9618
**Category:** Get Help
**Created:** [April 13, 2017, 9:36am UTC](https://community.xibo.org.uk/t/error-get-https-registry-1-docker-io-v2/9618 "2017-04-13T09:36:32Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![alex](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/alex/32/5782_2.png) [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [April 13, 2017, 10:13am UTC](https://community.xibo.org.uk/t/error-get-https-registry-1-docker-io-v2/9618/6 "2017-04-13T10:13:17Z")

</div>

If you can’t work around the proxy issues, you can transfer the images out of band.

So on a machine without proxy, run the following:

```
docker pull xibosignage/xibo-xmr:release_1.8.1
docker pull xibosignage/xibo-cms:release_1.8.1
docker pull mysql:5.6
docker save xibosignage/xibo-xmr:release_1.8.1 > xmr.tar.gz
docker save xibosignage/xibo-cms:release_1.8.1 > cms.tar.gz
docker save mysql:5.6 > mysql.tar.gz

```

Copy those three tar.gz files over to the production box, then run

```
docker load -i xmr.tar.gz
docker load -i cms.tar.gz
docker load -i mysql.tar.gz

```

Then do your `docker-compose up -d` or whatever as normal, and it won’t need to download those images.

---

_[View the full topic](https://community.xibo.org.uk/t/error-get-https-registry-1-docker-io-v2/9618)._