docker run -i -t -p 80:80 ricardoamaro/drupal8 337ms Fri Jul 6 00:38:50 2018
**** MySQL data found on /var/lib/mysql/ ****
**** /var/www/html/web/index.php found ****
grep: /var/www/html/web/sites/default/settings.php: No such file or directory
Starting Drupal installation. This takes a while. Consider using the --notify global option. [ok]
sh: 1: /usr/sbin/sendmail: not found
Installation complete. [ok]
Unable to send email. Contact the site administrator if the problem persists. [error]
Congratulations, you installed Drupal! [status]
memcache was enabled successfully. [ok]
The following extensions will be enabled: memcache
------------------------- GENERATED USERS CREDENTIALS ----------------------------------
DRUPAL: http://172.17.0.2 with user/pass: admin/admin
MYSQL : http://172.17.0.2/adminer.php drupal/sohh8Meequau or root/Ee8ew9xef6ee
SSH : ssh root@172.17.0.2 with user/pass: root/Ee8ew9xef6ee
Please report any issues to https://github.com/ricardoamaro/drupal8-docker-app
USE CTRL+C TO STOP THIS APP
------------------------------ STARTING SERVICES ---------------------------------------
2018-07-05 19:09:01,529 INFO daemonizing the supervisord process
2018-07-05 19:09:01,529 INFO supervisord started with pid 16
2018-07-05 19:09:02,575 INFO spawned: 'httpd' with pid 40
2018-07-05 19:09:02,577 INFO spawned: 'sshd' with pid 41
2018-07-05 19:09:02,589 INFO spawned: 'memcached' with pid 43
2018-07-05 19:09:02,591 INFO spawned: 'mysqld' with pid 44
2018-07-05 19:09:03,594 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-05 19:09:03,594 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-05 19:09:03,594 INFO success: memcached entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-05 19:09:03,594 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
I am still getting the following issue:
This site can’t be reached
172.17.0.2 took too long to respond.
After following the steps ->
Terminal:
I am still getting the following issue: This site can’t be reached 172.17.0.2 took too long to respond.