Unable to docker upgrade 2.3.7 to 3.3.0 on Linux

To be completed by the original poster:

CMS Version

2.3.7

Installation Method

Docker

Operating System

Ubuntu 20.04.4 LTS

Issue

Docker upgrade method is still pulling old docker 2.3.7 release instead of 3.0.0 release. I can’t figure out how to get Xibo to pull down and update to 3.0.0 correctly. I have tried the pull method (see below) and I have tried manually downloading the docker config files and placing them in the correct directory. Neither approach works.

See the following commands I ran:

administrator@xibo:~$ sudo docker ps
[sudo] password for administrator:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
877158c74558 xibosignage/xibo-cms:release-2.3.7 “/entrypoint.sh” 19 hours ago Up 19 hours 127.0.0.1:8080->80/tcp administrator_cms-web_1
625484460c09 xibosignage/xibo-xmr:release-0.8 “/entrypoint.sh” 19 hours ago Up 19 hours 0.0.0.0:9505->9505/tcp, :::9505->9505/tcp, 50001/tcp administrator_cms-xmr_1
4a696fd94d6f mysql:5.6 “docker-entrypoint.s…” 19 hours ago Up 19 hours 3306/tcp administrator_cms-db_1
3d3aa408d73f ianw/quickchart “node --max-http-hea…” 19 hours ago Up 19 hours 3400/tcp administrator_cms-quickchart_1

administrator@xibo:~$ sudo docker-compose down
Stopping administrator_cms-web_1 … done
Stopping administrator_cms-xmr_1 … done
Stopping administrator_cms-db_1 … done
Stopping administrator_cms-quickchart_1 … done
Removing administrator_cms-web_1 … done
Removing administrator_cms-xmr_1 … done
Removing administrator_cms-db_1 … done
Removing administrator_cms-quickchart_1 … done
Removing network administrator_default

administrator@xibo:~$ sudo docker pull xibosignage/xibo-cms:latest
latest: Pulling from xibosignage/xibo-cms
Digest: sha256:08039defbf444147ae6272513c4d3b9a116b491005030f47c266e87129895f6b
Status: Image is up to date for xibosignage/xibo-cms:latest ← this is weird. It’s not the latest version.
docker.io/xibosignage/xibo-cms:latest

administrator@xibo:~$ sudo docker pull xibosignage/xibo-cms:release-3.3.0
release-3.3.0: Pulling from xibosignage/xibo-cms
9621f1afde84: Already exists
5260dc798a69: Pull complete
3a254d5daeca: Pull complete
f2163afffc75: Pull complete
e4e734e92efe: Pull complete
e294733064af: Pull complete
92bed206e46a: Pull complete
35c1b416027f: Pull complete
9db4ec10015a: Pull complete
f4083f02808c: Pull complete
7b5bd75505b1: Pull complete
b616e6e83f4d: Pull complete
4cd5d6e0cdb5: Pull complete
Digest: sha256:14239f66c580824496daf5458644458eda43d21e495abfc0e7a2fceb1af9d2a7
Status: Downloaded newer image for xibosignage/xibo-cms:release-3.3.0
docker.io/xibosignage/xibo-cms:release-3.3.0

administrator@xibo:~$ sudo docker-compose -f cms_custom-ports.yml up -d
Creating network “administrator_default” with the default driver
Creating administrator_cms-db_1 … done
Creating administrator_cms-quickchart_1 … done
Creating administrator_cms-xmr_1 … done
Creating administrator_cms-web_1 … done
administrator@xibo:~$ sudo docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bf32f7ec906f xibosignage/xibo-cms:release-2.3.7 “/entrypoint.sh” 4 seconds ago Up 3 seconds 127.0.0.1:8080->80/tcp administrator_cms-web_1
9970a24e5d19 ianw/quickchart “node --max-http-hea…” 7 seconds ago Up 4 seconds 3400/tcp administrator_cms-quickchart_1
ad74074f720a mysql:5.6 “docker-entrypoint.s…” 8 seconds ago Up 4 seconds 3306/tcp administrator_cms-db_1
d0ea06d133fb xibosignage/xibo-xmr:release-0.8 “/entrypoint.sh” 8 seconds ago Up 4 seconds 0.0.0.0:9505->9505/tcp, :::9505->9505/tcp, 50001/tcp administrator_cms-xmr_1

I figured out my own issue.

I had to manually download the docker files, and replace cms_custom-ports.yml with a copy of cms_custom-ports.yml.template. I then had to copy the ports section from my old cms_custom-ports.yml to the new cms_custom-ports.yml. Then I was able to run a “sudo docker-compose -f cms_custom-ports.yml up -d” command and everything works as expected.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.