Xibo 1.8 Upgrade - Docker?

[robyholmes]

Hi All,

 

I'm looking to upgrade to Xibo 1.8 but all this Docker business is confusion me. Currently Xibo is running on a server 2012 R2 VM on a Hyper-V host. I've installed XAMPP to provide the webserver and MySQL database.

 

Xibo now suggest moving to Docker before moving to 1.8. I can't install Docker CE (Windows 10 only) so I downloaded and installed Docker Toolbox. This however fails the Vx check before starting. However I'm lost as to what Docker is providing or doing? The instructions seem to be all over the place.

 

Has anyone moved to 1.8? With or without Docker?

 

Thank you in advanced.

[robk]

Any one else doing this? Looking at the same thing...

[FN-GM]

I am also confused by it!

 

We run Xibo 1.7.9 on an Ubuntu server. I tried the old fashioned way ignoring the docker but couldn't get it to function.

[mjk]

However I'm lost as to what Docker is providing or doing?

 

So the purpose of Docker is to be able to run an application (Xibo) on any infrastructure, regardless of the operating system (notwithstanding windows, but that doesn't get much use in the cloud). ie you can quickly provision a system of your choosing: google cloud, Azure or even a linux server or all it's different flavours. Provided docker is installed then the application will be guaranteed to work because docker will bring across all of the dependencies for that app.

It's really very cool.

 

I've no experience with xibo, but the general premis is that you:

install docker

download the docker image

run the image.

 

https://docs.docker.com/engine/reference/run/#general-form

Edited April 6, 2017 by mjk

[robyholmes]

So the purpose of Docker is to be able to run an application (Xibo) on any infrastructure, regardless of the operating system (notwithstanding windows, but that doesn't get much use in the cloud). ie you can quickly provision a system of your choosing: google cloud, Azure or even a linux server or all it's different flavours. Provided docker is installed then the application will be guaranteed to work because docker will bring across all of the dependencies for that app.

It's really very cool.

 

I've no experience with xibo, but the general premis is that you:

install docker

download the docker image

run the image.

 

https://docs.docker.com/engine/reference/run/#general-form

 

This was my understanding from reading the website, but Xibo's instructions don't make it sound that easy at all!

 

My first issue is getting Docker to install and run. Docker CE won't run on anything but Windows 10 it seems (From a Windows POV) so installed Docker Toolbox but that uses Hypervisor which isn't supported in my VM (I'm on Server 2012 R2 Hyper V).

[mb2k01]

I haven't done this at my place yet, but was reading up on it.

It looks like you can still do the install / upgrade without Docker - but its fairly clear they want everyone to switch.

Instructions for non-docker installation or upgrade: Xibo Documentation

[ADMaster]

I upgraded mine to docker 1.8 a couple weeks ago and searched here first. There were no posts yet.

Anyway, I'm running mine on ubuntu so can't speak for the Windows side.

I setup a new 16.04 VM and did not install apache or mysql. I just installed docker and ssh. Docker handled the LAMP stack.

 

The docker docs were confusing at first I missed the command to install docker compose.

This guide https://docs.docker.com/compose/install/

Will tell you how to install compose, but the links for Ubuntu / Windows etc is just for docker. You need to install docker first then go to git hub to install compose.

https://github.com/docker/compose/releases

 

Once you have compose the rest of the docs are straight forward.

download and extract the tar I used /opt for my location

copy and edit the config.env and put in the mysql password.

create the listed paths under shared to copy in the import.sql backup and your media library.

run the docker-compose up -d command.

 

In my upgrade the secret key did not follow so my clients were not communicating at first. Log in and enter in the previous secret key.

Now change the hostname / IP to match the old xibo VM and everything should work.

[TechMonkey]

Only had a quick look but it appears you will need Server 2016 to run Docker on Windows, rather than it trying to run on a hypervisor.

 

Yay.

[robyholmes]

Only had a quick look but it appears you will need Server 2016 to run Docker on Windows, rather than it trying to run on a hypervisor.

 

Yay.

 

Looks like this will be my first 2012 R2 to 2016 upgrade then.

[ITGuyNW]

Yeah I was hoping to upgrade to the latest Xibo 1.8.1 but this Docker thing has me scratching my head. There are instructions to do it without Docker which seem similar to how it installs now but I don't know If I lose any functionality etc doing it that way.

[mavhc]

Looks like this will be my first 2012 R2 to 2016 upgrade then.

 

Just install a debian vm or something

[xibodan]

We switched to Docker for several reasons, the principle one being the introduction of Push Messaging (via something called ZeroMQ). ZeroMQ can be difficult to install, so wrapping it all up in a "docker" container made a lot of sense to us. In the past we've also spent many many hours on support incidents that turned out to be a problem with the environment rather than Xibo - Docker eliminates this as everyone is effectively running on the same environment.

 

We found Docker easy to get to grips with, having used it with other software packages, however I can understand that it is something new to learn. We've tried our best with the installation process and the information we've presented - however there are complaints about it being unclear. Dockers own instructions are not fantastic, which doesn't help. Unfortunately for more our instructions bleed into Docker instructions, the less clear it gets.

 

There are two main pages:

- Install Docker (Xibo Documentation)

- Install Xibo (Xibo Documentation)

 

If you have Docker working already, getting a fully working Xibo system running on Port 80 is a case of:

- Download and extract the release archive

- Copy and edit config.env.template

- Run `docker-compose up -d`

 

A "custom installation", which is an installation via the traditional method of configuring your own web server and database, is very much still an option and is covered in our user manual under "Custom Installation". We've said that we might not be able to provide community support for issues with this type of installation because if there is an issue we can't recreate in a Docker install, it is most likely an environment issue. We will still do our best to help, but issues of this nature might ultimately need commercial support.

[ITGuyNW]

Fed up with this Docker nonsense. Trying to get it to run was bad enough but now it won't download the build properly. Always hangs on at least one download. Whoever decided at Xibo to go down this route has really messed up.

[mavhc]

Are you running on windows or linux?

[xibodan]

Whoever decided at Xibo to go down this route has really messed up.

 

It was a joint decision amongst the project maintainers, but principally it was me that pushed for the change.

 

I still believe it was the right decision, however I would encourage anyone that doesn't want to use Docker to simply not use Docker.

 

As mentioned above there is a section in the manual that deals with custom installations - there are a few additional changes required for 1.8, but nothing too troublesome for someone with a little technical background.

 

As for your issue of it not pulling builds - it will be trying to connect to Docker hub (an online repository for Docker containers), perhaps something is blocking that connection.

[mavhc]

Probably a proxy needs settings up. Seems there's a lot of people who've never used docker, or linux. It's worth learning, containers are being embraced by everyone, including microsoft

[ModeratelyGruntled]

Hi there

 

Apologies for jumping in!

 

This will be my fourth or fifth Xibo installation but the first using Docker. Server 2012R2. Apache is on there as well for other purposes but I'm giving docker a crack.

 

I've think I've installed docker (toolbox) and I think I've extracted the CMS. However when opening VirtualBox I can't 'Find the Docker Virtual Machine (often called default)'.

 

docker-machine ip returns 'No machine names specified and no 'default' machine exists.

 

I'm sure I haven't extracted the CMS correctly, or maybe I've extracted the wrong file? c:\users\xibo\xibo-docker contains:

 

cms_custom-ports.yml.template, cme_remote-mysql.yml

config.env.template (copied, edited and saved as config.env)

config.env.template-remote-mysql

docker-compose-yml

license

readme.md

 

Any help with the above appreciated!

 

I think the move to docker is/will be a good thing - what kind of IT staff would we be if we weren't catalysts for change - however I echo those sentiments above that the installation guides do seem a little unwieldy at first, especially if you've no previous with docker.

Edited June 23, 2017 by ModeratelyGruntled

[xibodan]

You've got the right archive and extracted in the right place, so everything looks good there. The only thing to watch out for is that the Apache installation you already have on the host machine will most likely be using Port 80, so you may want to follow the section regarding "using different ports": Xibo Documentation

 

However when opening VirtualBox I can't 'Find the Docker Virtual Machine (often called default)'.

docker-machine ip returns 'No machine names specified and no 'default' machine exists.

 

I believe this means that the Docker install itself wasn't able to install correctly - on Windows Docker uses a small VM to orchestrate various Docker commands and the creation of containers, etc.

 

I've looked through our guide, and it appears that the Docker documentation has moved around again, and the link we've got in the manual is for an overview page rather than the actual installation instructions which are here: https://docs.docker.com/toolbox/toolbox_install_windows/ - were you able to find these OK?

[ModeratelyGruntled]

You've got the right archive and extracted in the right place, so everything looks good there. The only thing to watch out for is that the Apache installation you already have on the host machine will most likely be using Port 80, so you may want to follow the section regarding "using different ports": Xibo Documentation

 

I believe this means that the Docker install itself wasn't able to install correctly - on Windows Docker uses a small VM to orchestrate various Docker commands and the creation of containers, etc.

 

I've looked through our guide, and it appears that the Docker documentation has moved around again, and the link we've got in the manual is for an overview page rather than the actual installation instructions which are here: https://docs.docker.com/toolbox/toolbox_install_windows/ - were you able to find these OK?

 

Thanks for the reply - I neglected to mention I'm trying to install this on an existing VM (hyper-V). It appears installing docker on an already virtualised platform isn't supported. Is this the case?

[Arthur]

It appears installing docker on an already virtualised platform isn't supported. Is this the case?

Docker can be installed in a Linux VM running on Hyper-V. i.e.

 

sudo su
curl -sSL https://get.docker.com/ | sh

[TechMonkey]

Thanks for the reply - I neglected to mention I'm trying to install this on an existing VM (hyper-V). It appears installing docker on an already virtualised platform isn't supported. Is this the case?

 

No sure if you've seen my previous post but it looks server 2016 can handle Docker, so if you can spin up a Server 2016 instance within your platform you should be able to run it. I have no experience of this though and I'm not sure if this would lead to running VMs within VMs!

[ITGuyNW]

I've gone back now to 1.7.9. On three occasions, Docker/Xibo forgot my layouts etc after restarting the pc. Even implementing the "fix" it only brought one half finished layout back.

[ADMaster]

I'm running my docker xibo on Hyper-v 2016 host and ubuntu 16.04 lts VM.

[gh5000]

I've gone back now to 1.7.9. On three occasions, Docker/Xibo forgot my layouts etc after restarting the pc. Even implementing the "fix" it only brought one half finished layout back.

 

Using the default settings, you must extract/install the Xibo CMS inside the C:\Users directory for correct operation. Using an alternative location will cause your uploaded content and layouts to be lost.

from Xibo Documentation

 

Was this your issue @executiverocker?

[synaesthesia]

Xibo can do one. Docker is a joke as it is, and Xibo just worked beforehand.

Anything that claims "We do this, just like a hypervisor but we're not a hypervisor" whilst in fact, being exactly that is a little Appleish and not deserving the time of day.