Thank you for the feed back. I agree that MYSQL_ROOT_PASSWORD should not be needed. And it might be able to be removed after the initial database creation. I just could not get the database container to actually create the database without it. Not sure if it is a strange DSM thing(there are many with DSM6), or what, but if I get some more time I will see about investigating that.
In the mean time if anyone else wants to try Alex’s suggestion on their DSM 6.0 and DSM 6.1 devices that would be great.
First of all BIG THANKS to you two guys. Your my hero - in fact I plan to have 2 frames on my desktop for at least a month, to remind me of that crazy work You are doing to help us DOCKER DUMMYS with Synology - THANKS, A HUNDRED, cslaughter, and alex.
I tried to follow your instruction. I can see that image are running but where do I into the web interface?
when I run the image in docker terminal, it starts up but stops again when connecting to DB creation. I use phpMyAdmin as SQL, when you say MySQL, do you then mean “MySQL” only place I can find that is also on docker regi.
And Docker… well is the one I try to learn:slight_smile:
I still feel like I am in that category of Docker Dummy’s. But I see much potential with Docker and DSM6. Very easy upgrades, small compact hardware roll outs, ability to do load balancing, easy backup and system transfers, and more.
The web interface should be https://yourdomain.com. I have setup a sub-domain for my installation and a SSL cert to go with it. So mine is something like https://cms.domain.com.
I am not sure I follow on this. Are you saying that the cms-web container on the terminal window starts then stops? I think that is normal when it doesn’t have anything to do. If you are seeing the cms-db container start and stop, I saw that when I did not have the environment variables correct. I would delete your cms-db container, remove everything from the database folder, stop the cms-web container. Then rebuild the cms-db container, then start it. Look at the cmd-db log in docker and see if you see the main database being created. If that looks good and it is staying up, then I would start the cms-web containter. Look at the cms-db log again and see if you see that Xibo configured somethings. If that all looks good, then try to access the cms. If you cannot, please post back with any errors and screen shots of the docker info pages for the cms-db and cms-web containers.
Yes in the docker registry if you search for mysql, the first result should be “mysql”. I am currently using 5.7.18 that I selected when downloading the image, 5.6 should also work fine.
Thanks for your effort to make a guide on how to install xibo on dsm 6.x synology.
I have really tried to install bit by bit from your guide, and it just won’t work.
No matter how I try to install with dozens of combinations it always stops with, docker xibo cms-db can´t connect to mysql.
I have tried to just install mysql 5.6 with no description in volume, port settings, links and environment. Mysql just restart in a constant loop. I have also tried to install mysql on best practice, then mysql runs as a standalone app inside docker whiteout any connection with xibo-cms.
I usually get the log message “ERROR 2005 (HY000): Unknown MySQL server host ‘mysql’ (0)” or “cannot find Mysql host” I really want this to work, but no matter how I try it seems to stuck with the connection with mysql inside docker. Outside port 3306 is taken by Maria db and phpMyAdmin. I also tried to uninstall both with same result other than I can choose port 3306 outside port. So, what am I doing wrong.
The issue with environment variable “MYSQL_ROOT_PASSWORD” that was not needed told me that mysql is installed in docker but you write in your guide that” now you should see 3 containers” and that puzzles me because cms-xmr, cms-db and cms-web is 3, but what about mysql?
Is it possible for you to specify, how you should install mysql inside docker?
I hope you can help me, it would mean a lot.
Thanks, in advanced
I also have MariaDB running and did not need to configure special ports.
Are you completely removing the “cms-db” between each failed attempt at setting this up? If not, then that will causing problems and the setup will not get completed. When the “cms-db” runs the first time, it creates the database and user access based on the givin variables. If they are not correct, the only way to fix that is to destroy the “cms-db” docker container and then recreate it. It took me a while to get it correct. I think the biggest mistake that can be made when following the guide, is starting the “cms-db” before all the variables configured.
Can you post a screen shot of how you configured the variables for the cms-db container? Please mask username, password, and anything else you do not want people to have.
SOLVED OMG - the magic word was "cms-db IS the mysql"
Because in your guide you wrote: Now cms-db
_Click on “xibosignage/xibo-cms-release_1.8.X” and click launch
It should be “click on mysql version image you have downloded” instead…
everything is runing first time.
THANKS A LOT "NOT in a sarcastic manner I am truly thrilled"
why oh why dident I listen to myself the first minute i was reading your guide "I was wondering why do I have to launce the xibo-cms-release twice? well… they have there reason.
thank you for your very useful guide. I’m trying to get this setup running using
DiskStation DS412+
DSM 6.1.2-15132
Docker 1.11.2-0329
mySQL 5.6.36
Xibo Signage 1.8.1
However, I experience problems starting up the mySQL-database:
Initializing database
2017-06-27 09:17:24 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-06-27 09:17:24 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
2017-06-27 09:17:24 0 [Note] /usr/sbin/mysqld (mysqld 5.6.36) starting as process 35 …
2017-06-27 09:17:24 35 [Warning] Can’t create test file /var/lib/mysql/cms-db.lower-test
2017-06-27 09:17:24 35 [Warning] Can’t create test file /var/lib/mysql/cms-db.lower-test
a/usr/sbin/mysqld: Can’t change dir to ‘/var/lib/mysql/’ (Errcode: 13 - Permission denied)
2017-06-27 09:17:24 35 [ERROR] Aborting
2017-06-27 09:17:24 35 [Note] Binlog end
2017-06-27 09:17:24 35 [Note] /usr/sbin/mysqld: Shutdown complete
Any ideas on this? Any hint would be helpful, as I’m totally new to docker… The directories certainly exist (I named it ‘database’ instead of ‘datbase’ as in your guide - a typo?)
The “datbase” is a typo. Thank you for bring that to my attention. I would fix it, but for some reason I cannot edit the post anymore (@Peter ??)
Are you completely removing the “cms-db” between each failed attempt at setting this up? If not, then that will cause problems and the setup will not get completed. When the “cms-db” runs the first time, it creates the database and user access based on the given variables. If they are not correct, the only way to fix that is to destroy the “cms-db” docker container and then recreate it. It took me a while to get it correct. I think the biggest mistake that can be made when following the guide, is starting the “cms-db” before all the variables configured.
EDIT:
I looked at that error a bit closer and it looks like a permissions issue
2017-06-27 09:17:24 35 [Warning] Can’t create test file /var/lib/mysql/cms-db.lower-test
2017-06-27 09:17:24 35 [Warning] Can’t create test file /var/lib/mysql/cms-db.lower-test
a/usr/sbin/mysqld: Can’t change dir to ‘/var/lib/mysql/’ (Errcode: 13 - Permission denied)
When you created the folders on the Synology box, does the SYSTEM have full control permissions? Mine show my user, and for some reason, that http has read/write access. Not sure that should be. When I get some free time…(not sure when that would be) I might try shutting everything down, remove the http and try firing it backup.
I’ve set up the whole DSM from the scratch, now it works!!! Thank you very, very much for your efforts!
The problem, I assume, was that I had a native instance of MariaDB installed prior on the DSM. It was disabled, but its configuration should have caused the trouble…
The way to update the Containers on the Synology is not like the upgrade instructions. (I was hoping for something easier, if someone can see a better way, please let me know)
Here is the short version of what to do. I will expand on it, I am sure at some point.
First note that you will need to make sure you have a working backup, as suggested in the upgrade instructions. If you followed my guide, you should look here for the files: /volume1/web/xibo-docker/web/backup.
Also note that DSM6 has some quarks. One of them is that even if you disable a container, you cannot setup a new container with the same ports. So what this means is that when you are ready to shutdown the old container and bring up the new one, we need to change, or delete the old container first.(I prefer change as a fail-safe)
You will want to go to the Docker registry and downloadxibosingage/xibo-cms:latest.
One that is download you will need to configure it using all of the same settings as the previous container. The guide above has them, IF you used those to begin with. Remember that you will need to shutdown the previous CMS container, and then change the ports on it’s settings, before configuring the new container. I also recommend changing the name to xxxx.old and then name the new container what the old one was named.
Once that is done, fire it up and wait a few mins before trying to access the portal. Then it will probably have an upgrade wizard, click next, or what not. It should succeed. Now you should be up to date.
I followed precisely the tutorial and everything went smoothly.
The problem is that when I connect to the xibo web interface, it asks me for a username and password that is not specified in your procedure.
Can you tell us the credentials or tell me how I can create them.
While I don’t have a synology box to go through the guide, I’d assume the default CMS login credentials will be the same as usual in Xibo docker installations ie
But I see much potential with Docker and DSM6. Very easy upgrades, small compact hardware roll outs, ability to do load balancing, easy backup and system transfers, and more.
