Ok Thanks i’ll take a look at that
Im using toolbox version 17.03
In that case the link I shared above doesn’t apply.
If you’re running with toolbox, you need to run docker-compose from the Docker Toolbox Quickstart Console - not from Windows cmd or Powershell.
I have opened that and it been sat there for 10 minutes saying downloading a file called boot2docker.iso from github - must be a large file!
38MB I believe - according to their release page.
So once I have manage to set this docker thing up. Am i able to move it from computer to computer? Do those computers have to have docker installed?
Thanks
Yes and yes.
It requires Docker to run. It could be a Windows or a Linux server with Docker on it. You’d stop the containers on the source machine, copy over your “shared” directory (which is created when you start the CMS for the first time) and config.env/docker-compose.yml files, and run docker-compose up -d and the whole lot transfers over.
SO I thihk im getting somewhere, I’ve run the command now and its completed but im a bit stuck, the instructions say -
Thisis will bootstrap and start your Xibo CMS. The CMS will be fully installed with the default credentials.
Username: Xibo_admin
Password: password
You should log on to the CMS straight away and change the password on that account.
You can log on to the CMS at http://localhost. If you configured an alternative port number (see below), then be sure to add that to the URL - so for example http://localhost:8080
But there is nothing at localhost…?
It can take a minute or two to get everything installed and running.
If it’s not up shortly, then what output do you get from
docker-compose ps
That all looks good.
You get nothing at all in a browser accessing http://localhost from the same computer as you’re running the containers on?
yeah, it just says localhost refused to connect.
Is there meant to be any files populated in my folder as all the files look exactly that same as before, the shared/cms/library folders that the instructions said to create have nothing added to them, the all the library files i copied into but no files in the cms folder.
You should have a db folder created inside the shared folder, which contains files like ibdata1, ib_logfile0 etc
If it’s still not up, lets see the logs:
docker-compose logs
Am i being really stupid, i cant see what it saves the logs
It prints them right to the console so you can see them:
$ docker-compose logs
Attaching to xibodocker_cms-web_1, xibodocker_cms-db_1, xibodocker_cms-xmr_1
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-web_1 | MySQL started
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.19.0.4. Set the ‘ServerName’ directive globally to suppress this message
Yeah saw that, i was thinking it would produce a fail i could send you
$ docker-compose logs
Attaching to xibodocker_cms-web_1, xibodocker_cms-db_1, xibodocker_cms-xmr_1
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-web_1 | MySQL started
cms-web_1 | ERROR 1146 (42S02) at line 1: Table ‘cms.version’ doesn’t exist
cms-web_1 | New install
cms-web_1 | Provisioning Database
cms-web_1 | Configuring Database Settings
cms-web_1 | Setting up Maintenance
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
cms-db_1 | Initializing database
cms-db_1 | 2017-03-24 14:57:01 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-24 14:57:01 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 33 …
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Database physically writes the file full: wait…
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
cms-db_1 | 2017-03-24 14:57:01 33 [Warning] InnoDB: New log files created, LSN=45781
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Doublewrite buffer not found: creating new
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Doublewrite buffer created
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-24 14:57:01 33 [Warning] InnoDB: Creating foreign key constraint system tables.
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Foreign key constraint system tables created
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Creating tablespace and datafile system tables.
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Tablespace and datafile system tables created.
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: 5.6.35 started; log sequence number 0
cms-db_1 | 2017-03-24 14:57:01 33 [Note] Binlog end
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-24 14:57:01 33 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-24 14:57:03 33 [Note] InnoDB: Shutdown completed; log sequence number 1625977
cms-db_1 |
cms-db_1 |
cms-db_1 | 2017-03-24 14:57:03 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-24 14:57:03 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 56 …
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: 5.6.35 started; log sequence number 1625977
cms-db_1 | 2017-03-24 14:57:03 56 [Note] Binlog end
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-24 14:57:03 56 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-24 14:57:05 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 b3857bbe56e2 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-24 14:57:06 0 [Note] mysqld (mysqld 5.6.35) starting as process 79 …
cms-db_1 | 2017-03-24 14:57:06 79 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-24 14:57:06 79 [Note] InnoDB: 5.6.35 started; log sequence number 1625987
cms-db_1 | 2017-03-24 14:57:06 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: 25d58aaa-10a2-11e7-84a8-0242ac120003.
cms-db_1 | 2017-03-24 14:57:06 79 [Warning] ‘user’ entry ‘root@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-24 14:57:06 79 [Warning] ‘user’ entry ‘@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-24 14:57:06 79 [Warning] ‘proxies_priv’ entry ‘@ root@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-24 14:57:06 79 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-24 14:57:06 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: aeD8vishutha8mogo8oohieY8keecha3
cms-db_1 | 2017-03-24 14:57:07 79 [Warning] ‘proxies_priv’ entry ‘@ root@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 |
cms-db_1 | 2017-03-24 14:57:07 79 [Warning] ‘proxies_priv’ entry ‘@ root@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-24 14:57:07 79 [Note] mysqld: Normal shutdown
cms-db_1 |
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Giving 0 client threads a chance to die gracefully
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Event Scheduler: Purging the queue. 0 events
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down slave threads
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Forcefully disconnecting 0 remaining clients
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Binlog end
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'partition’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_FIELDS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_INDEXES’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_SYS_TABLES’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_CONFIG’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_DELETED’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_METRICS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMPMEM’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMP_RESET’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_CMP’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_LOCK_WAITS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_LOCKS’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'INNODB_TRX’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] Shutting down plugin 'InnoDB’
cms-db_1 | 2017-03-24 14:57:07 79 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-24 14:57:07 79 [Note] InnoDB: Starting shutdown…
cms-db_1 | 2017-03-24 14:57:09 79 [Note] InnoDB: Shutdown completed; log sequence number 1625997
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'BLACKHOLE’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'ARCHIVE’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'MRG_MYISAM’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'MyISAM’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'CSV’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'MEMORY’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'sha256_password’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'mysql_old_password’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'mysql_native_password’
cms-db_1 | 2017-03-24 14:57:09 79 [Note] Shutting down plugin 'binlog’
cms-db_1 | 2017-03-24 14:57:09 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-24 14:57:09 0 [Note] mysqld (mysqld 5.6.35) starting as process 1 …
cms-db_1 | 2017-03-24 14:57:09 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-24 14:57:09 1 [Note] InnoDB: 5.6.35 started; log sequence number 1625997
cms-db_1 | 2017-03-24 14:57:09 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
cms-db_1 | 2017-03-24 14:57:09 1 [Note] IPv6 is available.
cms-db_1 | 2017-03-24 14:57:09 1 [Note] - ‘::’ resolves to ‘::’;
cms-db_1 | 2017-03-24 14:57:09 1 [Note] Server socket created on IP: ‘::’.
cms-db_1 | 2017-03-24 14:57:09 1 [Warning] ‘proxies_priv’ entry ‘@ root@b3857bbe56e2’ ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-24 14:57:09 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-24 14:57:09 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)
That all looks fine.
I think I’ve twigged what it is.
With docker toolbox, they use Virtualbox on Windows to run the containers, so actually instead of http://localhost in your case, it will be http://ip.of.the.vm
The instructions we provide are based on Docker for Windows which works in the same way as Docker works on Linux.
So, you’ll need to find the IP of the virtual machine.
I believe you can get it by docker-machine ip with Toolbox.
OK, done that, got the ip, can ping it but still get nothing in the browser
Got it, had to add it to my proxy list
1 Like
Logged in ok, but none of my media was there, I must have gone wrong somewhere.
I’ll come back to this on monday. Thanks for all your help today, I know i must be being a pita but thankyou.