[FIXED] Fresh install over Docker on 18.04LTS fails

[Baylink]

To be completed by the original poster:

CMS Version

Whatever came from Docker pull on 2/27/20 evening; 2.1.something, presumably

Installation Method

Docker

Operating System

Ubuntu 18.04LTS up to date

Issue

After installing Docker from the installation instructions, and adjusting the port numbers in the cms_custom-ports.yml, I point a browser at the UI at 10.30.50.2:8080, and it gives me a small dialog box saying:

“”"
The CMS is temporarily off-line as an upgrade is in progress. Please check with your system administrator for updates or refresh your page in a few minutes.
“”"

Googling that led me to a few forum posts that all seem to be talking about upgrades; this is a fresh new install.

It may be that I misunderstood the port reassignment instructions. Here’s that file:

==8<==
version: “2.1”

services:
cms-db:
image: mysql:5.6
volumes:
- “./shared/db:/var/lib/mysql”
restart: always
environment:
- MYSQL_DATABASE=cms
- MYSQL_USER=cms
- MYSQL_RANDOM_ROOT_PASSWORD=yes
mem_limit: 1g
env_file: config.env
cms-xmr:
image: xibosignage/xibo-xmr:release-0.7
ports:
- “9505:9505”
restart: always
mem_limit: 256m
env_file: config.env
cms-web:
image: xibosignage/xibo-cms:release-2.1.0
volumes:
- “./shared/cms/custom:/var/www/cms/custom”
- “./shared/backup:/var/www/backup”
- “./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom”
- “./shared/cms/library:/var/www/cms/library”
- “./shared/cms/web/userscripts:/var/www/cms/web/userscripts”
restart: always
links:
- cms-db:mysql
- cms-xmr:50001
environment:
- XMR_HOST=cms-xmr
env_file: config.env
ports:
- “8080:80”
mem_limit: 1g
==8<==

Did I only want to change the cms-web port to answer on 8080 on the host IF? And leave the cms-xmr one as is?

[aponkye]

did you check to make sure docker-compose.yml has the same ports?

[Baylink]

I had not; the install guide at

https://xibo.org.uk/docs/setup/xibo-2-1-0-with-docker-on-ubuntu-18-04

is kind of unclear on this point.

Should the ports stanzas be the same between both files?

I’ve changed the -compose file so the web stanza is 8080:80 to match the custom-ports, and done a down and an:

docker-compose -f cms_custom-ports.yml up -d

but I still go to the error screen when I navigate to

http://10.30.50.2:8080/

[ If you prefer people to use the Docker deployment, it would be good to put at least some of this stuff in the install guide; most users won’t want to have to get married to Docker just to run Xibo… ]

[Baylink]

Here’s that docker-compose:

root@pano:/opt/xibo# cat docker-compose.yml
version: “2.1”

services:
cms-db:
image: mysql:5.6
volumes:
- “./shared/db:/var/lib/mysql”
environment:
- MYSQL_DATABASE=cms
- MYSQL_USER=cms
- MYSQL_RANDOM_ROOT_PASSWORD=yes
mem_limit: 1g
env_file: config.env
cms-xmr:
image: xibosignage/xibo-xmr:release-0.7
ports:
- “9505:9505”
mem_limit: 256m
env_file: config.env
cms-web:
image: xibosignage/xibo-cms:release-2.1.0
volumes:
- “./shared/cms/custom:/var/www/cms/custom”
- “./shared/backup:/var/www/backup”
- “./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom”
- “./shared/cms/library:/var/www/cms/library”
- “./shared/cms/web/userscripts:/var/www/cms/web/userscripts”
links:
- cms-db:mysql
- cms-xmr:50001
environment:
- XMR_HOST=cms-xmr
env_file: config.env
ports:
- “8080:80”
mem_limit: 1g

[Baylink]

FOLO: Since I see they’ve just released 2.3.0 to production, why’d I get 2.1 from Docker, not 2.2.something?

[Baylink]

One other note:

I moved the install to /xibo/ in the config.env, but going to

http:/10.30.50.2:8080/xibo/

did not help; same error dialog.

[Baylink]

CLOSED.

Restarted with the 2.3 docker tarball, and took more care with my ports changes, and now I have a login prompt.

[aponkye]

glad to hear you got it working