Docker for Windows: CMS is reset when I restart the host server

alex · March 9, 2017, 1:32pm

The password that you’ve given the container to use doesn’t match the one you’ve given the database.

So you remember I said in your earlier export that you had differing values for the MySQL password value.

If you’ve got nothing important in there, I would down your install (docker-compose down, then docker ps -a to ensure nothing is left running), remove everything inside your shared folder, and then bring it back up (docker-compose up).

That will give you a fresh install. You can then make a quick layout, reboot and check that the CMS comes back up on it’s own, and that your data persists before you start using it properly.

wolfcrust · March 9, 2017, 1:41pm

Hello alex. Thanx again!
I formated my PC…did everything from scratch and didnt put passwords anywhere... Im going to try again as you said. I`ll checkin with you in a while.
Thanx!

wolfcrust · March 9, 2017, 1:47pm

Alex,
did as you asked and my cmd got frozen at:
Microsoft Windows [Version 10.0.14393]
© 2016 Microsoft Corporation. Todos os direitos reservados.

C:\WINDOWS\system32>cd…

C:\Windows>cd…

C:>cd xibo-docker

C:\xibo-docker>docker-compose up
Creating network “xibodocker_default” with the default driver
Creating xibodocker_cms-xmr_1
Creating xibodocker_cms-db_1
Creating xibodocker_cms-web_1
Attaching to xibodocker_cms-xmr_1, xibodocker_cms-db_1, xibodocker_cms-web_1
cms-db_1 | Initializing database
cms-db_1 | 2017-03-09 13:41:44 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-09 13:41:44 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 33 …
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-web_1 | MySQL started
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Database physically writes the file full: wait…
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
cms-db_1 | 2017-03-09 13:41:44 33 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
cms-db_1 | 2017-03-09 13:41:45 33 [Warning] InnoDB: New log files created, LSN=45781
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Doublewrite buffer not found: creating new
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Doublewrite buffer created
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-09 13:41:45 33 [Warning] InnoDB: Creating foreign key constraint system tables.
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Foreign key constraint system tables created
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Creating tablespace and datafile system tables.
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Tablespace and datafile system tables created.
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: 5.6.35 started; log sequence number 0
cms-db_1 | 2017-03-09 13:41:45 33 [Note] Binlog end
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-09 13:41:45 33 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-09 13:41:47 33 [Note] InnoDB: Shutdown completed; log sequence number 1625977
cms-db_1 |
cms-db_1 |
cms-db_1 | 2017-03-09 13:41:47 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-09 13:41:47 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 56 …
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: 5.6.35 started; log sequence number 1625977
cms-db_1 | 2017-03-09 13:41:47 56 [Note] Binlog end
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-09 13:41:47 56 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-09 13:41:49 56 [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 a81ad2beb1aa 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 | 2017-03-09 13:41:49 0 [Note] mysqld (mysqld 5.6.35) starting as process 79 …
cms-db_1 | 2017-03-09 13:41:49 79 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-09 13:41:49 79 [Note] InnoDB: 5.6.35 started; log sequence number 1625987
cms-db_1 | 2017-03-09 13:41:49 79 [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: 255d15d4-04ce-11e7-b786-0242ac120003.
cms-db_1 | 2017-03-09 13:41:49 79 [Warning] ‘user’ entry ‘root@a81ad2beb1aa’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-09 13:41:49 79 [Warning] ‘user’ entry ‘@a81ad2beb1aa’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-09 13:41:49 79 [Warning] ‘proxies_priv’ entry ‘@ root@a81ad2beb1aa’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-09 13:41:49 79 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-09 13:41:49 79 [Note] mysqld: ready for connections.
cms-db_1 | Version: ‘5.6.35’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 0 MySQL Community Server (GPL)
cms-db_1 | Warning: Unable to load ‘/usr/share/zoneinfo/iso3166.tab’ as time zone. Skipping it.
cms-db_1 | Warning: Unable to load ‘/usr/share/zoneinfo/leap-seconds.list’ as time zone. Skipping it.
cms-db_1 | Warning: Unable to load ‘/usr/share/zoneinfo/zone.tab’ as time zone. Skipping it.
cms-db_1 | GENERATED ROOT PASSWORD: shai1AquaoReu7rofei1xuxohtua9oup
cms-db_1 | 2017-03-09 13:41:51 79 [Warning] ‘proxies_priv’ entry ‘@ root@a81ad2beb1aa’ ignored in --skip-name-resolve mode.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 |
cms-db_1 | 2017-03-09 13:41:51 79 [Note] mysqld: Normal shutdown
cms-db_1 |
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Giving 0 client threads a chance to die gracefully
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Event Scheduler: Purging the queue. 0 events
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down slave threads
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Forcefully disconnecting 0 remaining clients
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Binlog end
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'partition’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_FIELDS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_INDEXES’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_SYS_TABLES’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_CONFIG’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_DELETED’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_METRICS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMPMEM’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMP_RESET’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_CMP’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_LOCK_WAITS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_LOCKS’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'INNODB_TRX’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] Shutting down plugin 'InnoDB’
cms-db_1 | 2017-03-09 13:41:51 79 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-09 13:41:51 79 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-09 13:41:52 79 [Note] InnoDB: Shutdown completed; log sequence number 1625997
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'BLACKHOLE’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'ARCHIVE’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'MRG_MYISAM’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'MyISAM’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'CSV’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'MEMORY’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'sha256_password’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'mysql_old_password’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'mysql_native_password’
cms-db_1 | 2017-03-09 13:41:52 79 [Note] Shutting down plugin 'binlog’
cms-db_1 | 2017-03-09 13:41:52 79 [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 | 2017-03-09 13:41:52 0 [Note] mysqld (mysqld 5.6.35) starting as process 1 …
cms-db_1 | 2017-03-09 13:41:52 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-09 13:41:52 1 [Note] InnoDB: 5.6.35 started; log sequence number 1625997
cms-db_1 | 2017-03-09 13:41:52 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
cms-db_1 | 2017-03-09 13:41:52 1 [Note] IPv6 is available.
cms-db_1 | 2017-03-09 13:41:52 1 [Note] - ‘::’ resolves to ‘::’;
cms-db_1 | 2017-03-09 13:41:52 1 [Note] Server socket created on IP: ‘::’.
cms-db_1 | 2017-03-09 13:41:52 1 [Warning] ‘proxies_priv’ entry ‘@ root@a81ad2beb1aa’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-09 13:41:52 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-09 13:41:52 1 [Note] mysqld: ready for connections.
cms-db_1 | Version: ‘5.6.35’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | New install
cms-web_1 | Provisioning Database
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Configuring Database Settings
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Setting up Maintenance
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Enter password: ERROR 1045 (28000): Access denied for user ‘cms’@‘172.18.0.4’ (using password: NO)
cms-web_1 | Updating settings.php
cms-web_1 | Configuring Backups
cms-web_1 | Configuring Maintenance
cms-web_1 | Running maintenance
cms-web_1 | Starting cron
cms-web_1 | Starting webserver
cms-web_1 | AH00558: apache2: 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

alex · March 9, 2017, 1:54pm

You MUST specify a password for the CMS to use to connect to the database. You can’t simply ommit it.

Please down your containers, remove the contents of shared, and then re-read the Docker install guide in the manual here (http://xibo.org.uk/manual-tempel/en/install_cms.html), ensuring you create your config.env file, and set a password for the CMS to use in there before you bring the containers back up.

wolfcrust · March 9, 2017, 4:48pm

Thank you alex.
Done everything from scratch and managed to get it to work but… my first problema remains: everytime i restart it erases everything

alex · March 10, 2017, 12:44pm

Are files created inside the shared folder?

Particularly inside the db folder, there should be files for your MySQL database instance.

wolfcrust · March 13, 2017, 11:16am

Hi Alex.
yes, there´s cms,mysql and performance_schema folder, andauto.cnf.ib_logfile0, iblog_file1 and ibdata1 files

alex · March 13, 2017, 11:54am

So it’s creating what I’d expect.

What exactly are you doing to have it reset itself?

wolfcrust · March 13, 2017, 12:10pm

I just restart the computer…

alex · March 13, 2017, 12:38pm

and those files are still there once you’ve rebooted?

What comes up when you try and load the CMS after a reboot?

Does the same happen if you stop/start the containers (docker-compose stop, docker-compose start)?

wolfcrust · March 13, 2017, 12:47pm

Yes, the files are there.
When i load cms it goes to getting started guide (and resets password to :password).
Now I´m going to try docker-compose stop, docker-compose start without restarting the computer.

wolfcrust · March 13, 2017, 1:02pm

Alex,
did docker-compose stop, docker-compose start without restarting the computer.
CMD got frozen (see below) and reset everything as it does when i restart the computer:

C:\WINDOWS\system32>cd…

C:\Windows>cd…

C:>cd xibo-docker

C:\xibo-docker>docker-compose down
Stopping xibodocker_cms-web_1 … done
Stopping xibodocker_cms-db_1 … done
Stopping xibodocker_cms-xmr_1 … done
Removing xibodocker_cms-web_1 … done
Removing xibodocker_cms-db_1 … done
Removing xibodocker_cms-xmr_1 … done
Removing network xibodocker_default

C:\xibo-docker>docker-compose up
Creating network “xibodocker_default” with the default driver
Creating xibodocker_cms-xmr_1
Creating xibodocker_cms-db_1
Creating xibodocker_cms-web_1
Attaching to xibodocker_cms-xmr_1, xibodocker_cms-db_1, xibodocker_cms-web_1
cms-db_1 | 2017-03-13 12:53:42 0 [Note] mysqld (mysqld 5.6.35) starting as process 1 …
cms-db_1 | 2017-03-13 12:53:42 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-web_1 | MySQL started
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 2916191 in the ib_logfiles!
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Database was not shutdown normally!
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Starting crash recovery.
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Reading tablespace information from the .ibd files…
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Restoring possible half-written data pages
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: from the doublewrite buffer…
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-13 12:53:42 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-13 12:53:43 1 [Note] InnoDB: 5.6.35 started; log sequence number 2916191
cms-db_1 | 2017-03-13 12:53:43 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
cms-db_1 | 2017-03-13 12:53:43 1 [Note] IPv6 is available.
cms-db_1 | 2017-03-13 12:53:43 1 [Note] - ‘::’ resolves to ‘::’;
cms-db_1 | 2017-03-13 12:53:43 1 [Note] Server socket created on IP: ‘::’.
cms-db_1 | 2017-03-13 12:53:43 1 [Warning] ‘proxies_priv’ entry ‘@ root@0d6380cc66bf’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-13 12:53:43 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-13 12:53:43 1 [Note] mysqld: ready for connections.
cms-db_1 | Version: ‘5.6.35’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
cms-web_1 | DBVersion
cms-web_1 | 130
cms-web_1 | Updating settings.php
cms-web_1 | Configuring Backups
cms-web_1 | Configuring Maintenance
cms-web_1 | Running maintenance
cms-web_1 | Starting cron
cms-web_1 | Starting webserver
cms-web_1 | AH00558: apache2: 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

alex · March 13, 2017, 1:07pm

You did docker-compose down/up not stop/start. They are different commands completely.

wolfcrust · March 13, 2017, 1:22pm

sorry alex…
trying again…

wolfcrust · March 13, 2017, 1:28pm

Ok, just did it and everything is OK…my layout is still there and also the password.

C:\WINDOWS\system32>cd…

C:\Windows>cd…

C:>cd xibo-docker

C:\xibo-docker>docker-compose stop
Stopping xibodocker_cms-web_1 … done
Stopping xibodocker_cms-db_1 … done
Stopping xibodocker_cms-xmr_1 … done

C:\xibo-docker>docker-compose start
Starting cms-db … done
Starting cms-xmr … done
Starting cms-web … done

C:\xibo-docker>

alex · March 13, 2017, 1:51pm

So stop/start is all that happens when you restart the machine, unless you’re running some other commands manually either before or after you reboot the machine?

wolfcrust · March 13, 2017, 4:11pm

no, no other commands, just restart the machine.
I now tried to mount the container in a new user with admin rights but the result is the same after reboot…everithing´s gone

alex · March 13, 2017, 4:24pm

I’m afraid I don’t know in that case.

You might get some assistance from the Docker forums instead - as they may know why your data isn’t persisting.

I’ve tried it here over and over and nothing I do replicates the issue you’re having.

wolfcrust · March 13, 2017, 4:38pm

Alex,
I´m looking at docker and here´s something I might be doing wrong: do we run Windows or Linux containers?
now I´m running Linux container and if I try to mount the cms in Windows container I always get the message:

C:\Users\administrator\Documents\xibo-docker>docker-compose up -d
ERROR: client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

alex · March 13, 2017, 4:52pm

You could try changing the top version line in the docker-compose.yml file to read

version: "2.1"

There’s a bug here which looks like it might relate:

If that works, I can build that in to the next release without issue.