I’m trying to update Xibo to 1.8.1 but I got this error:

Creating network “xibodocker_default” with the default driver
Pulling cms-xmr (xibosignage/xibo-xmr:release_1.8.1)…
ERROR: Get net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

No issues running the docker hello world test

docker run hello-world

It could be a proxy issue ?

It’s definitely a connection issue. I presume you’ve retried a few times?

docker run hello-world won’t download anything if you’ve already run it once before, so that may not be diagnostic

yes, I have tested many times :frowning:
I’m in contact with our network team to see if we can bypass the proxy, I have no problem with standard apt commands.

I presume when you say “update” you have a working 1.8.0 install with Docker? So the proxy setup you had was working before?

Is your HTTP_PROXY environment variable set appropriately? apt has it’s own configuration and so the two aren’t valid tests.

It’s complicated, I have prepared the virtual machine using VMWare Workstation and a non-proxed connection, it worked well, then I have deployed the VM to prouction ESXi environment (that’s behind a proxy).
I have configured the Linux box proxy parameters( I have no problems with apt-get update etc etc) but I’m stuck with Docker.
I will move again the VM from ESXi to VMWare for updating, then I will re-deploy it but it’s a waste of time :frowning:


Also, I cannot ping the remote server:


Pinging [] with 32 bytes of data:
Request timed out.
Request timed out.

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.

I can’t either, but I can pull from it. Those aren’t our servers. They’re the DockerHub public registry.

As I mentioned, apt uses different proxy settings to almost every other Linux command line tool that uses proxy settings. That apt works is not therefore diagnostic. Please check that when you run env in your console, the HTTP_PROXY environment variable is set and has the correct value.

There’s a way to download these files without use Docker ?

You need to use docker to download them because they are stored as multiple layers, each in it’s own file. Docker downloads and merges the appropriate layers to deliver the image your require, and then can save that as a tar.gz

A good idea would be that you provide these files as offline upgrading option :wink:

They get rebuilt as the base image is updated (by Ubuntu in this case) so they’d be out of date, and potentially have security issues.

I’m not willing to commit to checking them every day and uploading them I’m afraid.


I have successfully update xibo using Docker offline option.
Unfortunately the proxy cannot be modified to allow Docker to pull the package :frowning:

It just uses https so that seems very strange to me. It would mean that your proxy doesn’t allow HTTPS traffic through :confused:

Very difficult to sort out… our proxy is a bit “nazi” for not approved connections.
Anyway the offline installation is really a good thing !