Hi, I have been trying install Xibo on a Windows Server 2016 Essentials System. I have used the “Docker on other Windows 64bit” installation process. It was somewhat working, however the shared folders would not create. I tried it with the Xibo zip file in C:\Users\ and C:\Users{username}\Documents. In both cases the shared files did not create. The Xibo files were configured and had full user permissions. Does anyone have any thoughts or suggestions? Thanks, Drew
Could you tell me what have you done so far from instructions here please?
https://xibo.org.uk/manual/en/install_docker_winother_64bit.html
Is the docker toolbox installed and working?
You have downloaded and extracted the xibo-docker archive?
Have you edited the config.env and set the db password?
Then in docker toolbox quickstart terminal, cd to the path where you extracted the xibo-docker and run
docker-compose up -d
If you’re at this step, what does it say when you run it please?
if you do
docker ps -a
what does that show?
Hi Peter,
Thanks for the help! Answers to your questions are below.
Thanks,
Drew
Could you tell me what have you done so far from instructions here please?
https://xibo.org.uk/manual/en/install_docker_winother_64bit.html
- I have followed this processes and the associated Docker Toolbox on
Windows install process multiple times with the extracted xibo-docker
archive in multiple locations - I also upgraded VirtualBox to 5.2.6 as it suggested
Is the docker toolbox installed and working?
- It is working as far as I know. It does run “Hello World”
You have downloaded and extracted the xibo-docker archive?
- I have and attempted multiple installs (and uninstalls) with it in
different places:- C:\Users\Xibo\
- C:\Users{UserName}\Xibo\
- C:\Users{UserName}\Documents\Xibo\
- C:\Xibo\ Set as share in VitualBox
- I eventually even gave these folders full permissions for
user/everyone/admin - In none of these locations was the share folder created
Have you edited the config.env and set the db password?
- Yes, password and email settings
- I do have a mySQL server running, however I am not using it for this
project. I do not believe this is causing the issues as mySQL for XiBo
is running in VurtualBox. At least I think it is not effecting it. I
did try a cms_remote-mysql install once. It did not work either
(although I am not sure it was really connected to mySQL Server)
Then in docker toolbox quickstart terminal, cd to the path where you
extracted the xibo-docker and rundocker-compose up -d
If you’re at this step, what does it say when you run it please?
This is with xibo-docker archive in C:\Users{UserName}\Xibo\
drew@NDP-SRV1 MINGW64 /c/users/xibo
$ docker-compose up -d
Creating network "xibo_default" with the default driver
Pulling cms-db (mysql:5.6)...
5.6: Pulling from library/mysql
f49cf87b52c1: Pull complete
78032de49d65: Pull complete
837546b20bc4: Pull complete
9b8316af6cc6: Pull complete
28dd7bab809d: Pull complete
8b95be8b8d36: Pull complete
2c501037cc00: Pull complete
1abe484cca68: Pull complete
ca1153755154: Pull complete
e241550fcba4: Pull complete
Digest:
sha256:6e5ba1192843bda054090a1f7a8481054a0b1038457b3acb9043628e0443ed50
Status: Downloaded newer image for mysql:5.6
Pulling cms-xmr (xibosignage/xibo-xmr:release-0.6)...
release-0.6: Pulling from xibosignage/xibo-xmr
605ce1bd3f31: Pull complete
285be9d55387: Pull complete
2ff0d4d16077: Pull complete
8f89d7348d76: Pull complete
f909642f3610: Pull complete
b10d463189b0: Pull complete
Digest:
sha256:bc87431ffe275fc708acae688280e03a8c3c40fbc5054ac72bf308474d480fbc
Status: Downloaded newer image for xibosignage/xibo-xmr:release-0.6
Pulling cms-web (xibosignage/xibo-cms:release-1.8.5)...
release-1.8.5: Pulling from xibosignage/xibo-cms
605ce1bd3f31: Already exists
7de05deb663b: Pull complete
dfba7df6e78e: Pull complete
5747a6b30473: Pull complete
f9e12da7c241: Pull complete
cfad3c7a0913: Pull complete
50f2061fb2be: Pull complete
8a81739b8fa4: Pull complete
Digest:
sha256:16f9dde6c41f718da40681212a351d2fc9cf0d8a2ed104bb33e994b3d67278c6
Creating xibo_cms-db_1 ... done
Creating xibo_cms-xmr_1 ... done
Creating xibo_cms-xmr_1 ...
Creating xibo_cms-web_1 ... done
drew@NDP-SRV1 MINGW64 /c/users/xibo
$
if you do
docker ps -a
what does that show?
drew@NDP-SRV1 MINGW64 /c/users/xibo
$ docker ps -a
CONTAINER ID IMAGE
COMMAND CREATED STATUS
PORTS NAMES
aa3128ed4a01 xibosignage/xibo-cms:release-1.8.5
"/entrypoint.sh" About a minute ago Up About a minute
0.0.0.0:80->80/tcp xibo_cms-web_1
6485da3b7771 xibosignage/xibo-xmr:release-0.6
"/entrypoint.sh" About a minute ago Up About a minute
0.0.0.0:9505->9505/tcp, 50001/tcp xibo_cms-xmr_1
db01e76d6dcd mysql:5.6
"docker-entrypoint.s…" About a minute ago Up About a minute
3306/tcp xibo_cms-db_1
97644ce7e468 hello-world
"/hello" 5 minutes ago Exited (0) 5 minutes
ago gifted_sammet
e0d28b4ed804 hello-world
"/hello" 10 minutes ago Exited (0) 10 minutes
ago trusting_easley
drew@NDP-SRV1 MINGW64 /c/users/xibo
$
The output of ps does appear to show that the containers are up - or at least they have not exited. When you say it was somewhat working - do you mean that the only problem is the shared folders not being created (and the rest otherwise worked) or do you mean that nothing is working?
What happens if you visit the IP address of the VM? Do you get an Xibo UI?
Can you temporarily run without -d - i.e. docker-compose up so that we get to see the full output? No need to use a new archive, stop/up on the current installation will be fine.
Hi Dan,
Thanks for the help! The answer to your questions are below:
When you say it was somewhat working - do you mean that the only problem is the shared folders not being created (and the rest otherwise worked) or do you mean that nothing is working?
The Xibo admin console works and I can run a display on the same machine. The shared folders are not creating in my c:\users\XiBo\ folder. This I believe is the reason that when I restart the computer to get to the Xibo console, I have to:
- run docker-compose down
- run docker-compose up -d
When I do this, I lose all changes I made previously. The Xibo Player (on the same computer) does connect also.
What happens if you visit the IP address of the VM? Do you get an Xibo UI?
Yes it works
Can you temporarily run without -d - i.e. docker-compose up so that we get to see the full output? No need to use a new archive, stop/up on the current installation will be fine.
Here is the output:
drew@NDP-SRV1 MINGW64 /c/users/xibo
$ docker-compose up
xibo_cms-db_1 is up-to-date
xibo_cms-xmr_1 is up-to-date
xibo_cms-web_1 is up-to-date
Attaching to xibo_cms-db_1, xibo_cms-xmr_1, xibo_cms-web_1
cms-db_1 | Initializing database
cms-db_1 | 2018-02-16 18:40:09 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
cms-db_1 | 2018-02-16 18:40:09 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2018-02-16 18:40:09 0 [Note] /usr/sbin/mysqld (mysqld 5.6.39) starting as process 32 ...
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Database physically writes the file full: wait...
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
cms-db_1 | 2018-02-16 18:40:09 32 [Warning] InnoDB: New log files created, LSN=45781
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Doublewrite buffer not found: creating new
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Doublewrite buffer created
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2018-02-16 18:40:09 32 [Warning] InnoDB: Creating foreign key constraint system tables.
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Foreign key constraint system tables created
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Creating tablespace and datafile system tables.
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Tablespace and datafile system tables created.
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: 5.6.39 started; log sequence number 0
cms-db_1 | 2018-02-16 18:40:09 32 [Note] Binlog end
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2018-02-16 18:40:09 32 [Note] InnoDB: Starting shutdown...
cms-db_1 | 2018-02-16 18:40:11 32 [Note] InnoDB: Shutdown completed; log sequence number 1625977
cms-db_1 |
cms-db_1 |
cms-db_1 | 2018-02-16 18:40:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
cms-db_1 | 2018-02-16 18:40:11 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2018-02-16 18:40:11 0 [Note] /usr/sbin/mysqld (mysqld 5.6.39) starting as process 55 ...
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: 5.6.39 started; log sequence number 1625977
cms-db_1 | 2018-02-16 18:40:11 55 [Note] Binlog end
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2018-02-16 18:40:11 55 [Note] InnoDB: Starting shutdown...
cms-db_1 | 2018-02-16 18:40:13 55 [Note] InnoDB: Shutdown completed; log sequence number 1625987
cms-db_1 |
cms-db_1 |
cms-db_1 |
cms-db_1 |
cms-db_1 | PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
cms-db_1 | To do so, start the server, then issue the following commands:
cms-db_1 |
cms-db_1 | /usr/bin/mysqladmin -u root password 'new-password'
cms-db_1 | /usr/bin/mysqladmin -u root -h 6a1077b1bc6a password 'new-password'
cms-db_1 |
cms-db_1 | Alternatively you can run:
cms-db_1 |
cms-db_1 | /usr/bin/mysql_secure_installation
cms-db_1 |
cms-db_1 | which will also give you the option of removing the test
cms-db_1 | databases and anonymous user created by default. This is
cms-db_1 | strongly recommended for production servers.
cms-db_1 |
cms-db_1 | See the manual for more instructions.
cms-db_1 |
cms-db_1 | Please report any problems at http://bugs.mysql.com/
cms-db_1 |
cms-db_1 | The latest information about MySQL is available on the web at
cms-db_1 |
cms-db_1 | http://www.mysql.com
cms-db_1 |
cms-db_1 | Support MySQL by buying support/licenses at http://shop.mysql.com
cms-db_1 |
cms-db_1 | Note: new default config file not created.
cms-db_1 | Please make sure your config file is current
cms-db_1 |
cms-db_1 | WARNING: Default config file /etc/mysql/my.cnf exists on the system
cms-db_1 | This file will be read by default by the MySQL server
cms-db_1 | If you do not want to use this, either remove it, or use the
cms-db_1 | --defaults-file argument to mysqld_safe when starting the server
cms-db_1 |
cms-db_1 | Database initialized
cms-db_1 | MySQL init process in progress...
cms-db_1 | MySQL init process in progress...
cms-db_1 | 2018-02-16 18:40:14 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
cms-db_1 | 2018-02-16 18:40:14 0 [Note] mysqld (mysqld 5.6.39) starting as process 83 ...
cms-db_1 | 2018-02-16 18:40:14 83 [Note] Plugin 'FEDERATED' is disabled.
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-02-16 18:40:14 83 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2018-02-16 18:40:15 83 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2018-02-16 18:40:15 83 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2018-02-16 18:40:15 83 [Note] InnoDB: 5.6.39 started; log sequence number 1625987
cms-db_1 | 2018-02-16 18:40:15 83 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: d4068161-1348-11e8-9b46-0242ac120002.
cms-db_1 | 2018-02-16 18:40:15 83 [Warning] 'user' entry 'root@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-db_1 | 2018-02-16 18:40:15 83 [Warning] 'user' entry '@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-db_1 | 2018-02-16 18:40:15 83 [Warning] 'proxies_priv' entry '@ root@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-db_1 | 2018-02-16 18:40:15 83 [Note] Event Scheduler: Loaded 0 events
cms-web_1 | MySQL started
cms-db_1 | 2018-02-16 18:40:15 83 [Note] mysqld: ready for connections.
cms-web_1 | ERROR 1146 (42S02) at line 1: Table 'cms.version' doesn't exist
cms-db_1 | Version: '5.6.39' socket: '/var/run/mysqld/mysqld.sock' port: 0 MySQL Community Server (GPL)
cms-web_1 | New install
cms-db_1 | Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
cms-web_1 | Provisioning Database
cms-db_1 | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
cms-web_1 | Configuring Database Settings
cms-db_1 | Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
cms-web_1 | Setting up Maintenance
cms-db_1 | GENERATED ROOT PASSWORD: aedieyeeGheithoWuroo1eeSh6ahbuwo
cms-web_1 | Protected Maintenance
cms-db_1 | 2018-02-16 18:40:17 83 [Warning] 'proxies_priv' entry '@ root@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-web_1 | Updating settings.php
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-web_1 | Configuring Maintenance
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-web_1 | Removing web/install/index.php from production container
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-web_1 | Running maintenance
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-web_1 | Starting cron
cms-db_1 | 2018-02-16 18:40:17 83 [Warning] 'proxies_priv' entry '@ root@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-web_1 | Starting webserver
cms-db_1 |
cms-web_1 | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.4. Set the 'ServerName' directive globally to suppress this message
cms-db_1 | 2018-02-16 18:40:17 83 [Note] mysqld: Normal shutdown
cms-db_1 |
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Giving 0 client threads a chance to die gracefully
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Event Scheduler: Purging the queue. 0 events
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down slave threads
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Forcefully disconnecting 0 remaining clients
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Binlog end
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'partition'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_DELETED'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_METRICS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMPMEM'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMP_RESET'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_CMP'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_LOCKS'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'INNODB_TRX'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] Shutting down plugin 'InnoDB'
cms-db_1 | 2018-02-16 18:40:17 83 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2018-02-16 18:40:17 83 [Note] InnoDB: Starting shutdown...
cms-db_1 | 2018-02-16 18:40:18 83 [Note] InnoDB: Shutdown completed; log sequence number 1625997
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'BLACKHOLE'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'ARCHIVE'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'MEMORY'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'MyISAM'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'MRG_MYISAM'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'CSV'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'sha256_password'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'mysql_old_password'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'mysql_native_password'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] Shutting down plugin 'binlog'
cms-db_1 | 2018-02-16 18:40:18 83 [Note] mysqld: Shutdown complete
cms-db_1 |
cms-db_1 |
cms-db_1 | MySQL init process done. Ready for start up.
cms-db_1 |
cms-db_1 | 2018-02-16 18:40:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
cms-db_1 | 2018-02-16 18:40:19 0 [Note] mysqld (mysqld 5.6.39) starting as process 1 ...
cms-db_1 | 2018-02-16 18:40:19 1 [Note] Plugin 'FEDERATED' is disabled.
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2018-02-16 18:40:19 1 [Note] InnoDB: 5.6.39 started; log sequence number 1625997
cms-db_1 | 2018-02-16 18:40:19 1 [Note] Server hostname (bind-address): '*'; port: 3306
cms-db_1 | 2018-02-16 18:40:19 1 [Note] IPv6 is available.
cms-db_1 | 2018-02-16 18:40:19 1 [Note] - '::' resolves to '::';
cms-db_1 | 2018-02-16 18:40:19 1 [Note] Server socket created on IP: '::'.
cms-db_1 | 2018-02-16 18:40:19 1 [Warning] 'proxies_priv' entry '@ root@6a1077b1bc6a' ignored in --skip-name-resolve mode.
cms-db_1 | 2018-02-16 18:40:19 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2018-02-16 18:40:19 1 [Note] mysqld: ready for connections.
cms-db_1 | Version: '5.6.39' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)
So we’ve proved that aside from the shared folders, everything is working as expected. 
This is the sole reason you’re having a problem and unfortunately I do not have a clear idea why that might be happening.
Usually it is because the Docker toolbox does not have permission to write to that folder - but it sounds like that folder is the logged in users folder?
It might be that we need to take a quick look at your system via Team Viewer - would you be agreeable to that? If so you can PM me the TeamViewer details (I would be connecting on Monday).
After connecting we discovered that the MySQL container wasn’t able to read the shared files it created. Adding the below solved the issue:
command: --innodb_use_native_aio=0
I also had to create the shared folder manually before docker would write anything to its mounted volumes - it is not clear whether this was part of the problem or not.
Hi
I am also facing the same problem.
Can u just explain where this command has to be added
ls it in docker-compose yml file ,under cms db.
i just added this and it shows a yml.scanner error(i added –innodb_use_native_aio=0 under cms db file /as 15 th line)