Here are the Docker logs. I am trying to run this on a fresh Ubuntu install on DigitalOcean with 512mb of RAM.
web_1 | 2017-09-11 10:38:03,633 CRIT Set uid to user 0
web_1 | 2017-09-11 10:38:03,668 INFO RPC interface 'supervisor' initialized
web_1 | 2017-09-11 10:38:03,669 INFO supervisord started with pid 11
web_1 | 2017-09-11 10:38:04,678 INFO spawned: 'stdout' with pid 14
web_1 | 2017-09-11 10:38:04,697 INFO spawned: 'php-fpm7' with pid 15
web_1 | 2017-09-11 10:38:04,709 INFO spawned: 'nginx' with pid 16
web_1 | 2017-09-11 10:38:06,027 INFO success: stdout entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
web_1 | 2017-09-11 10:38:06,028 INFO success: php-fpm7 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
web_1 | 2017-09-11 10:38:06,028 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
web_1 | 2017/09/11 10:40:04 [info] 17#17: *3 client closed connection while waiting for request, client: 91.64.208.111, server: 0.0.0.0:80
web_1 | 2017/09/11 10:40:08 [info] 17#17: *4 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: 172.17.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.1-fpm.sock:", host: "localhost"
web_1 | 172.17.0.1 - - [11/Sep/2017:10:40:08 +0000] "GET / HTTP/1.1" 499 0 "-" "curl/7.47.0"
mariadb_1 | Initializing database
mariadb_1 |
mariadb_1 | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
mariadb_1 | To do so, start the server, then issue the following commands:
mariadb_1 |
mariadb_1 | '/usr/bin/mysqladmin' -u root password 'new-password'
mariadb_1 | '/usr/bin/mysqladmin' -u root -h password 'new-password'
mariadb_1 |
mariadb_1 | Alternatively you can run:
mariadb_1 | '/usr/bin/mysql_secure_installation'
mariadb_1 |
mariadb_1 | which will also give you the option of removing the test
mariadb_1 | databases and anonymous user created by default. This is
mariadb_1 | strongly recommended for production servers.
mariadb_1 |
redis_1 | 1:C 11 Sep 10:38:02.063 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | _._
redis_1 | _.-``__ ''-._
redis_1 | _.-`` `. `_. ''-._ Redis 3.2.10 (00000000/0) 64 bit
redis_1 | .-`` .-```. ```\/ _.,_ ''-._
redis_1 | ( ' , .-` | `, ) Running in standalone mode
redis_1 | |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
redis_1 | | `-._ `._ / _.-' | PID: 1
redis_1 | `-._ `-._ `-./ _.-' _.-'
mariadb_1 | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
mariadb_1 | MySQL manual for more instructions.
mariadb_1 |
mariadb_1 | Please report any problems at http://mariadb.org/jira
mariadb_1 |
mariadb_1 | The latest information about MariaDB is available at http://mariadb.org/.
mariadb_1 | You can find additional information about the MySQL part at:
mariadb_1 | http://dev.mysql.com
mariadb_1 | Consider joining MariaDB's strong and vibrant community:
mariadb_1 | https://mariadb.org/get-involved/
mariadb_1 |
redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
redis_1 | | `-._`-._ _.-'_.-' | http://redis.io
redis_1 | `-._ `-._`-.__.-'_.-' _.-'
redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
redis_1 | | `-._`-._ _.-'_.-' |
redis_1 | `-._ `-._`-.__.-'_.-' _.-'
redis_1 | `-._ `-.__.-' _.-'
redis_1 | `-._ _.-'
mariadb_1 | Database initialized
mariadb_1 | MySQL init process in progress...
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] mysqld (mysqld 10.2.8-MariaDB-10.2.8+maria~jessie) starting as process 95 ...
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Uses event mutexes
redis_1 | `-.__.-'
redis_1 |
redis_1 | 1:M 11 Sep 10:38:02.068 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 11 Sep 10:38:02.068 # Server started, Redis version 3.2.10
redis_1 | 1:M 11 Sep 10:38:02.069 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 11 Sep 10:38:02.069 * The server is now ready to accept connections on port 6379
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Compressed tables use zlib 1.2.8
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Using Linux native AIO
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Number of pools: 1
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Using SSE2 crc32 instructions
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [ERROR] InnoDB: mmap(137560064 bytes) failed; errno 12
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
mariadb_1 | 2017-09-11 10:38:06 139981159606144 [Note] InnoDB: Starting shutdown...
mariadb_1 | *** Error in `mysqld': double free or corruption (out): 0x00000038e0b3d0a0 ***
mariadb_1 | 170911 10:38:06 [ERROR] mysqld got signal 6 ;
mariadb_1 | This could be because you hit a bug. It is also possible that this binary
mariadb_1 | or one of the libraries it was linked against is corrupt, improperly built,
mariadb_1 | or misconfigured. This error can also be caused by malfunctioning hardware.
mariadb_1 |
mariadb_1 | To report this bug, see https://mariadb.com/kb/en/reporting-bugs
mariadb_1 |
mariadb_1 | We will try our best to scrape up some info that will hopefully help
mariadb_1 | diagnose the problem, but since we have already crashed,
mariadb_1 | something is definitely wrong and this may fail.
mariadb_1 |
mariadb_1 | Server version: 10.2.8-MariaDB-10.2.8+maria~jessie
mariadb_1 | key_buffer_size=134217728
mariadb_1 | read_buffer_size=2097152
mariadb_1 | max_used_connections=0
mariadb_1 | max_threads=102
mariadb_1 | thread_count=0
mariadb_1 | It is possible that mysqld could use up to
mariadb_1 | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759896 K bytes of memory
mariadb_1 | Hope that's ok; if not, decrease some variables in the equation.
mariadb_1 |
mariadb_1 | Thread pointer: 0x0
mariadb_1 | Attempting backtrace. You can use the following information to find out
mariadb_1 | where mysqld died. If you see no messages after this, something went
mariadb_1 | terribly wrong...
mariadb_1 | stack_bottom = 0x0 thread_stack 0x49000
mariadb_1 | mysqld(my_print_stacktrace+0x2e)[0x38dec1df6e]
mariadb_1 | mysqld(handle_fatal_signal+0x305)[0x38de658845]
mariadb_1 | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f4fe7094890]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4fe51b1067]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4fe51b2448]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(+0x731b4)[0x7f4fe51ef1b4]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(+0x7898e)[0x7f4fe51f498e]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(+0x79696)[0x7f4fe51f5696]
mariadb_1 | mysqld(+0x94f4cc)[0x38de9284cc]
mariadb_1 | mysqld(+0x94a062)[0x38de923062]
mariadb_1 | mysqld(+0x80d8b2)[0x38de7e68b2]
mariadb_1 | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x38de65ab54]
mariadb_1 | mysqld(+0x4e8dc5)[0x38de4c1dc5]
mariadb_1 | mysqld(_Z11plugin_initPiPPci+0x8aa)[0x38de4c346a]
mariadb_1 | mysqld(+0x43c10e)[0x38de41510e]
mariadb_1 | mysqld(_Z11mysqld_mainiPPc+0x65e)[0x38de4191ae]
mariadb_1 | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4fe519db45]
mariadb_1 | mysqld(+0x4335fd)[0x38de40c5fd]
mariadb_1 | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mariadb_1 | information that should help you find out what is causing the crash.
mariadb_1 | /usr/local/bin/docker-entrypoint.sh: line 100: 95 Aborted (core dumped) "$@" --skip-networking --socket="${SOCKET}"
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process in progress...
mariadb_1 | MySQL init process failed.
Here are the Docker logs. I am trying to run this on a fresh Ubuntu install on DigitalOcean with 512mb of RAM.