database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
database_1   | standard_init_linux.go:178: exec user process caused "no such file or directory"
backend_1    | standard_init_linux.go:178: exec user process caused "no such file or directory"
backend_1    | standard_init_linux.go:178: exec user process caused "no such file or directory"
redis_1      | 1:C 16 May 07:35:22.308 # 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.8 (00000000/0) 64 bit
redis_1      |   .-`` .-```.  ```\/    _.,_ ''-._
redis_1      |  (    '      ,       .-`  | `,    )     Running in standalone mode
redis_1      |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
redis_1      |  |    `-._   `._    /     _.-'    |     PID: 1
redis_1      |   `-._    `-._  `-./  _.-'    _.-'
redis_1      |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1      |  |    `-._`-._        _.-'_.-'    |           http://redis.io
redis_1      |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1      |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1      |  |    `-._`-._        _.-'_.-'    |
redis_1      |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1      |       `-._    `-.__.-'    _.-'
redis_1      |           `-._        _.-'
redis_1      |               `-.__.-'
redis_1      |
redis_1      | 1:M 16 May 07:35:22.312 # 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 16 May 07:35:22.312 # Server started, Redis version 3.2.8
redis_1      | 1:M 16 May 07:35:22.312 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue
 run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after TH
P is disabled.
redis_1      | 1:M 16 May 07:35:22.313 * DB loaded from disk: 0.001 seconds
redis_1      | 1:M 16 May 07:35:22.313 * The server is now ready to accept connections on port 6379