My Xibo rc3 blew up

After following the instructions here http://xibo.org.uk/manual-tempel/en/release_notes_1.8.0-rc3.html to upgrade from rc2 and add docker. I get this
ERROR: In file ‘./docker-compose.yml’ service ‘version’ doesn’t have any configuration options. All top level keys in your docker-compose.yml must map to a dictionary of configuration options.

I don’t know what I’ve done but any help would be greatly appreciated. To be honest I just don’t have another 10 hours of troubleshooting in me,

Sounds like your version of docker-compose is too old to work with our docker-compose file.

docker-compose -v

I would imagine a version lower that 1.6, which is the minimum required.

How did you install Docker? Following our instructions should have given you the latest version (1.8.1 as far as I am aware).

Yep I’m at 1.5.2 guess Ill make a quick upgrade and try again , I installed according to instructions but when I ran it it said it wasnt there and to reinstall. Wrong directory maybe? Thank you

Sorry, when you ran what? Xibo?

You mean you got the Xibo installer instead of your existing installation which you tried to upgrade from 1.7? If so, can you send file listings from the folders you’ve created?

Thanks

Sorry I missed this question until now. I upgraded from 1.8 rc2 I followed instructions to add composer then followed instructions to move 1.8 rc3 to the xibo directory after shutting down 1.8 rc2 with destroy command leaving database intact. basically followed instructions as shown in upgrade procedures listed for rc2 to rc3 when I tried to run
docker-compose up
It said docker was not installed so I used CLI instructions for installing docker for ubuntu (Here is where I made my mistake I think) Within the Xibo-Docker-Master directory It installed but then I got the original error.
I’m sure I screwed this up so I decided this morning not to worry about it I didnt have that much in it anyway so I dumped that instance in Amazon AWS and I’m starting a new instance from scratch. I have all the artwork etc. Like I said I’m sure I messed it up :slight_smile:

OK, well if you are happy to start fresh then we will leave it at that :slight_smile:

Interesting I installed using
wget -qO- https://get.docker.com/ | sh
per instructions here
http://xibo.org.uk/manual-tempel/en/install_docker.html
then tried to use docker-compose -v and got this back
The program ‘docker-compose’ is currently not installed. You can install it by typing:
sudo apt install docker-compose

I get docker compose version 1.5.2 where did i screw up again? lol

The docker compose you get in apt is old which is why we suggested installing using the Docker sh file - however, perhaps that does not install the desired version of compose either! :frowning:

Perhaps this would provide some assistance: https://docs.docker.com/engine/installation/linux/ubuntu/#docker-ce ?

Same Error on Fresh install and fresh Instance
In file ‘./docker-compose.yml’ service ‘version’ doesn’t have any configuration options. All top level keys in your docker-compose.yml must map to a dictionary of configuration options.

ls gives me this
root@ip-172-31-18-61:/home/ubuntu/xibo-docker-master# ls
cms_custom-ports.yml.template config.env.template-remote-mysql README.md
cms_dev.yml.template containers test
cms_remote-mysql.yml docker-compose.yml
config.env LICENSE

root@ip-172-31-18-61:/home/ubuntu/xibo-docker-master# ls
cms_custom-ports.yml.template  config.env.template-remote-mysql  README.md
cms_dev.yml.template           containers                        test
cms_remote-mysql.yml           docker-compose.yml
config.env                     LICENSE
root@ip-172-31-18-61:/home/ubuntu/xibo-docker-master# cd /
root@ip-172-31-18-61:/# apt-get install \
>     apt-transport-https \
>     ca-certificates \
>     curl \
>     software-properties-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version (20160104ubuntu1).
apt-transport-https is already the newest version (1.2.19).
curl is already the newest version (7.47.0-1ubuntu2.2).
software-properties-common is already the newest version (0.96.20.5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ip-172-31-18-61:/# curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
OK
root@ip-172-31-18-61:/# apt-key fingerprint 0EBFCD88
pub   4096R/0EBFCD88 2017-02-22
      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
uid                  Docker Release (CE deb) <docker@docker.com>
sub   4096R/F273FCD8 2017-02-22

root@ip-172-31-18-61:/# sudo add-apt-repository \
>    "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
>    $(lsb_release -cs) \
>    stable"
root@ip-172-31-18-61:/# apt upddate
E: Invalid operation upddate
root@ip-172-31-18-61:/# apt update
Hit:1 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:3 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:5 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
Hit:6 https://download.docker.com/linux/ubuntu xenial InRelease
Fetched 306 kB in 0s (566 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@ip-172-31-18-61:/# apt install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker-ce is already the newest version (17.03.0~ce-0~ubuntu-xenial).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ip-172-31-18-61:/# apt-get install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker-ce is already the newest version (17.03.0~ce-0~ubuntu-xenial).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ip-172-31-18-61:/# docker run hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://cloud.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/engine/userguide/

This is the complete run from the CE install reccomended I realize I’ve been out of it for a while but this is making me feel like a complete idiot. If I didn’t have so much invested in this I would bang my head against the desk desk burn down the office and run screaming for the hills LOL

The bottom line is that your docker-compose installation is out of date - but i’ve reached the end of my knowledge for how to help you.

I will have to defer to @alex - he will comment as soon as he is able.

Thanx Dan I appreciate your patience and not coming through to strangle me :slight_smile:

if its any help I upgraded distro to 16.10 and installed docker including edge. Docker now reports back as
Docker version 17.03.0-ce, build 3a232c8
When I run docker -v
But running docker-compose -v gets me this
The program ‘docker-compose’ is currently not installed. You can install it by typing:
sudo apt install docker-compose
I am afraid to install docker-compose without hearing from you first as to where I should get docker-compose from. Is it just from the edge repository? if so then I am on latest and I should be able to just install correct?

You definitely don’t need to upgrade the OS.

You should be installing Docker from the official Docker repositories, by following their install guide. Once you do that, you’ll have the latest stable Docker.

I suspect you perhaps have multiple additional repositories installed for Docker, which is why there’s a problem.

With the official docker repositories on Ubuntu 16.04, I get:

# docker-compose -v
docker-compose version 1.9.0, build 2585387

# docker --version
Docker version 17.03.0-ce, build 60ccb22

In my /etc/apt/sources.list.d/docker.list file, I have:

deb https://apt.dockerproject.org/repo ubuntu-xenial main

Yours won’t be for xenial though if you’ve upgraded to 16.10.

Have a look through any other files in that directory, for Docker-related repositories you may have enabled, and remove those. Then apt-get update and apt-get upgrade and then finally if docker-compose isn’t installed, install it with apt-get install docker-compose

1 Like

Last login: Mon Mar 6 21:12:28 2017 from 66.102.228.76
ubuntu@ip-172-31-27-163:~$ docker --version
Docker version 17.03.0-ce, build 3a232c8
ubuntu@ip-172-31-27-163:~$ docker -v
Docker version 17.03.0-ce, build 3a232c8
ubuntu@ip-172-31-27-163:~$ docker-compose -v
docker-compose version 1.5.2, build unknown
ubuntu@ip-172-31-27-163:~$

I do not understand that 1.5.2 comes up even as edge install is there a way that I can tell it which version of compose to install?

It seems that docker-compose isn’t included in the docker-engine package which is the one that the Docker project ship.

I expect then the docker-compose package you’re seeing is from Ubuntu or elsewhere.

Try running which docker-compose and apt-cache policy docker-compose

What do they output? That will tell us where it’s coming from.

In any case, you’ll need to remove the packaged version (by running apt-get remove --purge docker-compose), then install following the instructions for the latest release here:

I’ll file a bug to update the documentation for that. Windows and Mac versions of docker-engine do come with it bundled.

Thank you at least I now know I haven’t gone crazy or forgotten how to follow instructions. Take that Alzheimers… And Thanks for checking in to this for me

This solved the issue thank again

2 Likes