# Can't view library

**URL:** https://community.xibo.org.uk/t/cant-view-library/11843
**Category:** Get Help
**Created:** [October 3, 2017, 7:26pm UTC](https://community.xibo.org.uk/t/cant-view-library/11843 "2017-10-03T19:26:31Z")
**Posts on this page:** 1
**Showing post:** 8

<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: [October 5, 2017, 12:58pm UTC](https://community.xibo.org.uk/t/cant-view-library/11843/8 "2017-10-05T12:58:05Z")

</div>

> [@ERROR: Get https://registry-1.docker.io/v2/](https://community.xibo.org.uk/t/error-get-https-registry-1-docker-io-v2/9618/6):
>
> 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…

You’d clearly choose the 1.8.2 images rather than 1.8.1 as shown in the example.

Once you have the images loaded on your machine and available, then you’d do the upgrade as normal (ie backup, put fresh docker-compose files in place, and then bring the updated containers up).

[https://xibo.org.uk/manual-tempel/en/upgrade\_docker.html](https://xibo.org.uk/manual-tempel/en/upgrade_docker.html)

---

_[View the full topic](https://community.xibo.org.uk/t/cant-view-library/11843)._