Issue Upgrading to v2.3.17

[Davor.N]

Today I tried to update Xibo CMS from 2.3.16 to 2.3.17 using Docker and got an error: “ERROR: filesystem layer verification failed for digest sha256:8043d1098a57270360038227c479e2c3f3f2b5826b8617931b9924a013758ceb”

[Davor.N]

[Davor.N]

I tried multiple times and always got the same error error.

[Davor.N]

I rolled back to version 2.3.16 and then tried to upgrade again to version 2.3.17. The identical error occurs again after command “docker-compose up -d”. Does anyone have any advice?

[Davor.N]

I tried with other versions of xibo-cms and the conclusion is that this error occurs with versions whose image is on Github (ghcr.io/xibosignage).

[gitthismoney]

i upgraded from 2.3.16 to .17 via github tar.gz release and had no probs

[Davor.N]

I’m using Xibo for Docker on computer with Windows 10 Enterprise (version 21H2). I suppose that you are using computer with Linux. I have problem only with image versions that are moved to Github – version 2.3.17 and versions 3.3.5 and higher. Docker version is 2.2.0.5.

[DanBW]

Hi Davor.N,

You could try running the command docker system prune -af which will delete all unused images, then try pulling that image again. Does the issue persist?

Many Thanks.

[alex]

Otherwise it might be a proxy configuration issue - worth checking your proxy server settings and that nothing is being blocked by any proxy you’re using.

[Davor.N]

Hi DanBW,
I tried the command “docker system prune -af” but the same error occurred again:

The error occurs with an item whose sha256 is 8043d1098a57270360038227c479e2c3f3f2b5826b8617931b9924a013758ceb
which in the manifest (https://github.com/xibosignage/xibo-cms/pkgs/container/xibo-cms/91302926?tag=release-2.3.17) is visible here:

[Davor.N]

Alex you were right what could have been the problem. The company’s IT department checked this problem and concluded that the problem is in the limitation of downloading images from Github. The solution was that IT downloaded the image (Package xibo-cms · GitHub) from outside the company network. After that, Xibo started working.