Dockerコンテナ内で扱う環境変数の定義とsedで環境変数の値に書き換える方法[ビルド時にはできないけどコンテナ内ではできた]

ビルドしたイメージはどこでも動く。

そんなイメージを作るためには、**環境変数の値をdocker-compose.ymlやDockerfileにベタ書き**することのないようにしなければなりません。

そこで、環境変数の値をDockerfile/docker-compose.ymlらに書くことなく、定義し、ビルドし、ひいてはsedでその環境変数の値に置換する方法を調べたので共有します。

こんなかんじに無事Hubotをcliから起動させることができました。
（slackのHubotのランプは緑に点灯し、ステータスはActive/Runnnig）
![restart-hubot.gif](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/341653/340dca24-4447-fac3-16fe-27c361a987b5.gif)

slack上で **!run show ansible** とpackを探したり、Actionを実行することもできます。
![pack-show-ansible.gif](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/341653/99aabfb6-c85c-47dc-1fce-5e172ce1f343.gif)


またビルド時にはコンテナ内のファイルの値を環境変数の値にsedすることはできませんでしたが、コンテナのなかでsedすることはできました。

そこで、何故詰まったのか、考えられる原因はどこなのかについても備忘録もかねて公開したいと思います。






#目次
- [コンテナ内で扱う環境変数の定義方法](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#コンテナ内で扱う環境変数の定義方法)
- [コンテナ内のファイルをsedで置換できない](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#コンテナ内のファイルをsedで置換できない)
- [考えられる原因](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#考えられる原因)
- [2019/09/23追記](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#20190923追記)
- [2019/09/27追記](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#20190927追記)
- [2019/09/27追記ここまでのまとめ](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#20190927追記ここまでのまとめ)


#コンテナ内で扱う環境変数の定義方法
- 環境変数とその値をdocker-compose.yml内に記載(環境変数の値は固定値)
- 環境変数をdocker-compose.yml内に記載(ビルド前に環境変数を定義できる)

```custom-filename.yml
    environment:
      - key=value  #docker-compose.ymlで定義
      - key        #export key=valueとコマンドを叩くか、~/.bashrcなどにexport key=valueと記載
    env_file:
      - conf/stackstorm.env
```

```
export HUBOT_SLACK_TOKEN='xoxb-your-token'
```

あるいは

```
$ sudo vi ~/.bashrc
export HUBOT_SLACK_TOKEN='xoxb-your-token'
```

src:
[Environment variables in Compose | Docker Documentation]
(https://docs.docker.com/compose/environment-variables)

#コンテナ内のファイルをsedで置換できない
問題はここから。
ビルドして、[images/stackstorm/bin/entorypoint.sh](https://github.com/gkzz/st2-docker-gkz/blob/dev-conf-env/images/stackstorm/bin/entrypoint.sh)でおこなっているsedができていませんでした、、。

```
$ docker-compose -f docker-compose-dev.yml up -d
Creating network "st2-docker-gkz_private" with driver "bridge"
Creating network "st2-docker-gkz_public" with driver "bridge"
Creating volume "st2-docker-gkz_mongo-volume" with default driver
Creating volume "st2-docker-gkz_mongo-configdb-volume" with default driver
Creating volume "st2-docker-gkz_postgres-volume" with default driver
Creating volume "st2-docker-gkz_rabbitmq-volume" with default driver
Creating volume "st2-docker-gkz_redis-volume" with default driver
Creating volume "st2-docker-gkz_stackstorm-packs-volume" with default driver
Creating volume "st2-docker-gkz_stackstorm-virtualenvs-volume" with default driver
Creating volume "st2-docker-gkz_stackstorm-configs-volume" with default driver
Creating volume "st2-docker-gkz_stackstorm-log-volume" with default driver
Creating st2-docker-gkz_postgres_1 ... done
Creating st2-docker-gkz_redis_1    ... done
Creating st2-docker-gkz_mongo_1    ... done
Creating st2-docker-gkz_rabbitmq_1 ... done
Creating st2-docker-gkz_stackstorm_1 ... done
$ docker-compose exec stackstorm bash
root@40c0e80dce83/#
```


###sedができているか確認

sedで書き換えたかった、以下の3つは全てsedできていませんでした。
- ST2_API_KEY
- HUBOT_ADAPTER
- HUBOT_SLACK_TOKEN
 
```
root@40c0e80dce83/# cat /opt/stackstorm/chatops/st2chatops.env | grep ST2_API_KEY
export ST2_API_KEY="${ST2_API_KEY}"
# (Uncomment ST2_AUTH_URL, ST2_AUTH_USERNAME, ST2_AUTH_PASSWORD and comment out ST2_API
```


```
root@40c0e80dce83:/# cat /opt/stackstorm/chatops/st2chatops.env | grep HUBOT_ADAPTER=slack
# export HUBOT_ADAPTER=slack
```

```
root@40c0e80dce83:/# cat /opt/stackstorm/chatops/st2chatops.env | grep HUBOT_SLACK_TOKEN
# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE
```

ん！？どういうことでしょうか？？


#考えられる原因
- sedがそもそも正しく書けていない
- 環境変数がそもそも正しく定義されていない
- **ビルド時に[images/stackstorm/bin/entorypoint.sh](https://github.com/gkzz/st2-docker-gkz/blob/dev-conf-env/images/stackstorm/bin/entrypoint.sh)に記載されているsedコマンドが想定通りに認識されていない→今回の原因？**
- ビルド時に[images/stackstorm/bin/entorypoint.sh](https://github.com/gkzz/st2-docker-gkz/blob/dev-conf-env/images/stackstorm/bin/entrypoint.sh)に記載されている環境変数が想定通りに値に変換されていない


####コンテナ内でsedコマンドを叩く
>- sedがそもそも正しく書けていない
>- 環境変数がそもそも正しく定義されていない

[考えられる原因](https://qiita.com/gkzz/items/fb3f8c1bd2398269a85e#考えられる原因)の上2つは、コンテナ内でsedできるかどうかで検証できそうなので、やってみます。

```
root@40c0e80dce83:/# export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'\$YOURBOTNAME'"}'); \
>sed -i -e 's/export ST2_API_KEY="\${ST2_API_KEY}"/export ST2_API_KEY='"\$ST2_API_KEY"'/' \
> -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \
> -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"\$HUBOT_SLACK_TOKEN"'/' \
> /opt/stackstorm/chatops/st2chatops.env
```
```
root@40c0e80dce83:/# cat /opt/stackstorm/chatops/st2chatops.env | grep ST2_API_KEY
export ST2_API_KEY=YOUR_KEY_XXXXXXXXXXXXXXXXXXXXXXXXXXX
```

####sedで置換されていることが確認できる
```
root@40c0e80dce83:/# cat /opt/stackstorm/chatops/st2chatops.env | grep HUBOT_ADAPTER=slack
export HUBOT_ADAPTER=slack
```

```
root@40c0e80dce83:/# cat /opt/stackstorm/chatops/st2chatops.env | grep HUBOT_SLACK_TOKEN
export HUBOT_SLACK_TOKEN=xoxb-your-token
```

####Hubotがslackで起動されることも確認
```
root@40c0e80dce83:/# st2ctl reload --register-all && service st2chatops restart | grep st2chatops
Registering content...[flags = --config-file /etc/st2/st2.conf --register-all]
/opt/stackstorm/st2/local/lib/python2.7/site-packages/cryptography/hazmat/primitives/constant_time.py:26: 
##### st2 components status #####
st2actionrunner PID: 161
(略)
st2chatops stop/waiting
st2chatops start/running, process 1186
```

以上から、ビルド時には効かなかったsedはコンテナ内のターミナル上では実行することが確認されました。

また、docker-compose upでsedする前と後でファイルの中身は変わっていないことから、最後の環境変数が想定通りの値に置換出来ていない可能性は考えにくいです。
そのため、原因は

>- ビルド時に[images/stackstorm/bin/entorypoint.sh](https://github.com/gkzz/st2-docker-gkz/blob/dev-conf-env/images/stackstorm/bin/entrypoint.sh)に記載されているsedコマンドが想定通りに認識されていない

と考えます。
ドキュメントを漁ったり、ググって類似ケースを調べては検証を重ねていますが、解決策は見つかっていません。

とはいえ、コンテナ内でsedして環境変数に書き換えることは出来たので、既存のpackの仕様確認とそれらのカスタマイズに着手することにします。
（ビルド時にst2chatopsの起動まで終えたかったのですが。）

P.S. もう一度docker-compose upするにはどうしたらよいか？
docker-compose downするだけではvolumeまで削除できないので、-vオプションをつけて実行した後、
改めてdocker-compose -f docker-compose-dev.yml up -dをすればいけました。

```
$ docker-compose down -v

Stopping st2-docker-gkz_stackstorm_1 ... done
Stopping st2-docker-gkz_redis_1      ... done
Stopping st2-docker-gkz_rabbitmq_1   ... done
Stopping st2-docker-gkz_postgres_1   ... done
Stopping st2-docker-gkz_mongo_1      ... done
Removing st2-docker-gkz_stackstorm_1 ... done
Removing st2-docker-gkz_redis_1      ... done
Removing st2-docker-gkz_rabbitmq_1   ... done
Removing st2-docker-gkz_postgres_1   ... done
Removing st2-docker-gkz_mongo_1      ... done
Removing network st2-docker-gkz_private
Removing network st2-docker-gkz_public
Removing volume st2-docker-gkz_mongo-volume
Removing volume st2-docker-gkz_mongo-configdb-volume
Removing volume st2-docker-gkz_postgres-volume
Removing volume st2-docker-gkz_rabbitmq-volume
Removing volume st2-docker-gkz_redis-volume
Removing volume st2-docker-gkz_stackstorm-packs-volume
Removing volume st2-docker-gkz_stackstorm-virtualenvs-volume
Removing volume st2-docker-gkz_stackstorm-configs-volume
Removing volume st2-docker-gkz_stackstorm-log-volume
$ docker-compose -f docker-compose-dev.yml up -d
（略）
$ docker-compose exec stackstorm bash
root@40c0e80dce83:/# 
```

参考:
環境変数の設定、ビルドの方法
- [Environment variables in Compose | Docker Documentation]
(https://docs.docker.com/compose/environment-variables)
- [docker ENV vs RUN export - Stack Overflow](https://stackoverflow.com/questions/33379393/docker-env-vs-run-export)

chatops周りの設定
- [StackStormでSlackによるChatOpsの設定をする | 俺的備忘録 〜なんかいろいろ〜](https://orebibou.com/2016/10/stackstorm%E3%81%A7slack%E3%81%AB%E3%82%88%E3%82%8Bchatops%E3%81%AE%E8%A8%AD%E5%AE%9A%E3%82%92%E3%81%99%E3%82%8B)
- [StackStormを使ってSlackからネットワーク装置を制御してみよう｜【技業LOG】技術者が紹介するNTTPCのテクノロジー｜【公式】NTTPC](https://www.nttpc.co.jp/technology/stackstorm.html)


P.P.S. Twitterもやってるのでフォローしていただけると泣いて喜びます！
[@gkzvoice](https://twitter.com/gkzvoice)


# 2019/09/23追記

>- ビルド時にimages/stackstorm/bin/entorypoint.shに記載されているsedコマンドが想定通りに認識されていない

左記の問題の原因について少し深堀してみたのでメモ。

- ビルド時にできなくて、ビルド後コンテナ内でできる。
- 後者はexec stackstorm bashとつけているから、ここらへんが怪しいのでは？

[検証用ブランチ](https://github.com/gkzz/st2-docker-gkz/tree/dev-conf-env-feature-exec)を切ってトライしたが、状況は変わらず。
変更箇所はこちら。

```images/stackstorm/bin/entrypoint.sh
#export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}')
#sed -i -e 's/export ST2_API_KEY="${ST2_API_KEY}"/export ST2_API_KEY='"$ST2_API_KEY"'/' \
#    -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \
#    -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \
#    /opt/stackstorm/chatops/st2chatops.env
#
#st2ctl reload --register-all && service st2chatops restart

exec /st2-docker/bin/sed-st2chatops-env.sh
```

**exec /st2-docker/bin/sed-st2chatops-env.sh**
と書くことができるようにsedコマンドを書いたシェルスクリプトを別途用意しました。

```images/stackstorm/bin/sed-st2chatops-env.sh
#!/bin/bash

ST2_API_KEY=$(st2 apikey create -k -m '{"name": "${YOURBOTNAME}"}')
sed -i -e "s/export ST2_API_KEY=\"${ST2_API_KEY}\"/export ST2_API_KEY=${ST2_API_KEY}/" \
    -i -e "s/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/" \
    -i -e "s/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN=${HUBOT_SLACK_TOKEN}/" \
    /opt/stackstorm/chatops/st2chatops.env

st2ctl reload --register-all && service st2chatops restart

```
参考:
[bash – docker entrypointスクリプトでexecを使用する目的は何ですか？](https://codeday.me/jp/qa/20190317/411415.html)



# 2019/09/27追記

###シェルスクリプトに書かれたsedが想定通りの動きをしていないのではないか
sedで書き換える値を環境変数で定義した後sedする一連のコマンドが書かれたシェルスクリプトをコンテナ内で走らせることができるか検証したところ、うまくいきました。

検証用のシェルスクリプトをこしらえる

```activate-hubot.sh 
#!/bin/bash

export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}'); \
sed -i -e 's/export ST2_API_KEY="${ST2_API_KEY}"/export ST2_API_KEY='"$ST2_API_KEY"'/' \
    -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \
    -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \
    /opt/stackstorm/chatops/st2chatops.env

st2ctl reload --register-all && service st2chatops restart
```

```
root@a6e3dcaa3bd9:/# source activate-hubot.sh 
Registering content...[flags = --config-file /etc/st2/st2.conf --register-all]
/opt/stackstorm/st2/local/lib/python2.7/site-packages/cryptography/hazmat/primitives/constant_time.py:26: CryptographyDeprecationWarning: Support for your Python version is deprecated. The next version of cryptography will remove support. Please upgrade to a 2.7.x release that supports hmac.compare_digest as soon as possible.
  utils.PersistentlyDeprecated2018,
2019-09-27 11:14:29,610 INFO [-] Connecting to database "st2" @ "mongo:27017" as user "None".
2019-09-27 11:14:29,614 INFO [-] Successfully connected to database "st2" @ "mongo:27017" as user "None".
2019-09-27 11:14:29,959 INFO [-] =========================================================
2019-09-27 11:14:29,960 INFO [-] ############## Registering triggers #####################

(略)

##### st2 components status #####
st2actionrunner PID: 131

(略)

st2sensorcontainer PID: 46
st2chatops is not running.
st2timersengine PID: 63

(略)

stop: Unknown instance: 
st2chatops start/running, process 889
root@a6e3dcaa3bd9:/# service st2chatops status
st2chatops start/running, process 889
root@a6e3dcaa3bd9:/# 
```

###Extension fieldという新パラメータ
左記のsedが書かれたシェルスクリプトの出力結果にmongo dbの文言があったことから、ビルドが完了してからでないとstackstormはmongo dbを確認できないのではないか？と考えました。
（表現に誤りがある場合はコメント欄にご指摘いただければうれしいです。）
早速、調べていたところ、docker-compose version 3.4から**Extension field**という新しいパラメータを発見！

```
2019-09-27 11:14:29,614 INFO [-] Successfully connected to database "st2" @ "mongo:27017" as user "None".
```

**docker-compose up -d**でビルドしたイメージをなんとかして**新たなDockerfileに引き継ぐ**ことが出来ればいける！？

そこで、[検証用ブランチ](https://github.com/gkzz/st2-docker-gkz/tree/dev-conf-env-feature-extends)を切ってビルドを試みました。

ここでは検証用に手を加えた箇所だけ記載します。

```docker-compose-dev.yml 
services: 
  stackstorm: 
    &stackstorm 
    image: stackstorm/stackstorm:${ST2_IMAGE_TAG:-latest} 
    build: 
      context: ./images/stackstorm/ 
@@ -39,6 +40,15 @@ services: 
      - ./conf/stackstorm.env:/st2-docker/env 
      #- ./images/stackstorm/config/st2chatops.env:/opt/stackstorm/chatops/st2chatops.env 
    dns_search: . 

   st2hubot: 
     <<: *stackstorm 
     container_name: st2hubot 
     build: 
         context: ./images/stackstorm/ 
         dockerfile: Dockerfile.hubot 
     volumes: 
       - ./images/stackstorm/bin/sed-st2chatops-env.sh:/st2-docker/bin/sed-st2chatops-env.sh |

### External Services 
```

```images/stackstorm/Dockerfile.dev
- ENTRYPOINT ["/st2-docker/bin/entrypoint.sh"] 
+ RUN ["/bin/bash", "-c", "/st2-docker/bin/entrypoint.sh"] 
```

継承先で使うDockerfile.hubot
新規に作成。

```images/stackstorm/Dockerfile.hubot
#FROM ubuntu:trusty

COPY bin/sed-st2chatops-env.sh /st2-docker/bin/sed-st2chatops-env.sh

#ENV ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}')
#RUN sed \
#    #-i -e 's/export ST2_API_KEY=\"${ST2_API_KEY}\"/export ST2_API_KEY='"$ST2_API_KEY"'/' \
#    -i -e 's/export HUBOT_ADAPTER=($HUBOT_ADAPTER)/export HUBOT_ADAPTER=slack/' \
#    -i -e 's/export HUBOT_SLACK_TOKEN=($HUBOT_SLACK_TOKEN)/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \
#    /opt/stackstorm/chatops/st2chatops.env
#    #./images/stackstorm/config/st2chatops.env

RUN export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}') ; \
RUN sed -i -e 's/export ST2_API_KEY=\"${ST2_API_KEY}\"/export ST2_API_KEY='"$ST2_API_KEY"'/' \
    -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \
    -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \
    /opt/stackstorm/chatops/st2chatops.env
RUN st2ctl reload --register-all && service st2chatops restart

```

新規に作成したDockerfile.hubotにsedコマンドは書いたので削除。

```images/stackstorm/bin/entrypoint.sh
 ( cd /etc/nginx/conf.d && ln -sf st2-base.cnf st2.conf ) 

export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}') 
sed -i -e 's/export ST2_API_KEY="${ST2_API_KEY}"/export ST2_API_KEY='"$ST2_API_KEY"'/' \ 
     -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \ 
     -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \ 
     /opt/stackstorm/chatops/st2chatops.env 

st2ctl reload --register-all && service st2chatops restart 
 #export ST2_API_KEY=$(st2 apikey create -k -m '{"name": "'$YOURBOTNAME'"}') 
#sed -i -e 's/export ST2_API_KEY="${ST2_API_KEY}"/export ST2_API_KEY='"$ST2_API_KEY"'/' \ 
#    -i -e 's/# export HUBOT_ADAPTER=slack/export HUBOT_ADAPTER=slack/' \ 
#    -i -e 's/# export HUBOT_SLACK_TOKEN=xoxb-CHANGE-ME-PLEASE/export HUBOT_SLACK_TOKEN='"$HUBOT_SLACK_TOKEN"'/' \ 
#    /opt/stackstorm/chatops/st2chatops.env 
#
#st2ctl reload --register-all && service st2chatops restart 

exec /sbin/init

```
ディレクトリ構成はこんなかんじです。

```
$ tree . -n 2 -d images/
.
├── bin
├── conf
├── docs
│   └── demo
├── images
│   └── stackstorm
│       ├── bin
│       │   └── sed-st2chatops-env.sh
│       └── config
├── runtime
│   ├── compose-1ppc
│   ├── entrypoint.d
│   └── st2.d
└── tutorial
    ├── actions
    │   └── workflows
    ├── policies
    └── rules
2 [error opening dir]
images/
└── stackstorm
    ├── bin
    │   └── sed-st2chatops-env.sh
    └── config

22 directories
```

継承するところでコケたようです。

```
$ docker-compose -f docker-compose-dev.yml up -d

Creating st2-docker-gkz_redis_1    ... done
Creating st2-docker-gkz_postgres_1 ... done
Creating st2-docker-gkz_mongo_1    ... done
Creating st2-docker-gkz_rabbitmq_1 ... done
Creating st2hubot                  ... 
Creating st2-docker-gkz_stackstorm_1 ... error

ERROR: for st2-docker-gkz_stackstorm_1  Cannot start service stackstorm: driver failed programming external connectivity on endpoint st2-docker-Creating st2hubot                    ... done1f69a6b98f): Bind for 0.0.0.0:443 failed: port is already allocated

ERROR: for stackstorm  Cannot start service stackstorm: driver failed programming external connectivity on endpoint st2-docker-gkz_stackstorm_1 (b8390f26aaf8b68266cbc496a2d14a0c88617928c328f426273e6b1f69a6b98f): Bind for 0.0.0.0:443 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.
```


コンテナ内に叩くsedコマンドを書いたシェルスクリプトをCOPYで置いてコンテナ内で走らせようかな爆。
(いかに頑張らずにコンテナを使うかを必死に頑張った結果笑)
、、、と若干心が折れかけたので、ここまで調べたことを整理し、結局何をどう解決すればよいか考え、進展があれば更新します。

# 2019/09/27追記ここまでのまとめ
### 本来コンテナ内で行うことをビルド時に行うことはできる？
- docker-compose up -dでコンテナを立ち上げた後おこなうコマンドの実行をビルドに含めること（Dockerfileないし、entorypoinst.shに追加すること）は可能なのか。

### 調べたこと
- docker-compose 3.4から追加されたExtension Fieldを使うと、イメージの継承？ができる
参考：docker-compose 3.4から追加されたExtension Fieldを使ってdocker-compose.yml でアンカー エイリアスを使う
https://qiita.com/kyusyukeigo/items/af20487162ff0a1a6cea


### エラーメッセージで気になるところ

>ERROR: for stackstorm  Cannot start service stackstorm: driver failed programming external connectivity on endpoint st2-docker-gkz_stackstorm_1 (略): Bind for 0.0.0.0:443 failed: **port is already allocated**
ERROR: Encountered errors while bringing up the project.

**port is already allocated**(ポート、もう割り当てられているよ)というところが怪しいです。
字面だけで判断すれば、extendのパラメータが上手く機能していない（＝別のイメージとして生成しようとしているからポートを割り当てようとしてエラーを踏んでいる）ということですよね、、、。

### 次に調べること
- 継承した後にやりたいこと（コンテナ内でコマンドを叩くことと同じこと）をするためのDockerfileの書き方
- Extension fieldの書き方
- 事前にdocker hubにpushしたイメージをpullしてsedする

<blockquote class="twitter-tweet"><p lang="ja" dir="ltr">、、、とリプして気づいたのが、一度ビルドしたイメージをdocker hubにpushし、それをpullしてビルドするという、、、。<br><br>よい方法なのか分かりませんが汗。<br><br>リプありがとうございます！！</p>&mdash; gkz (@gkzvoice) <a href="https://twitter.com/gkzvoice/status/1177590943391727616?ref_src=twsrc%5Etfw">September 27, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

[@jack_frost_will](https://twitter.com/jack_frost_will)さん、リプありがとうございます。
光が見えました。！！



参考:
[Extension fields Compose file version 3 reference | Docker Documentation](https://docs.docker.com/compose/compose-file/#extension-fields)


docker-compose logs -follow > dc.logしたら、数十分経ってもプロンプトが返ってこないのでctrl+cして強制終了させましたが、logです。

```
$ cat dc.log
Attaching to st2-docker-gkz_stackstorm_1, st2-docker-gkz_redis_1, st2-docker-gkz_mongo_1, st2-docker-gkz_rabbitmq_1, st2-docker-gkz_postgres_1
[33mredis_1       |[0m 1:C 27 Sep 12:55:47.733 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
[33mredis_1       |[0m 1:C 27 Sep 12:55:47.733 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=1, just started
[33mredis_1       |[0m 1:C 27 Sep 12:55:47.733 # Configuration loaded
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 * Running mode=standalone, port=6379.
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 # Server initialized
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 # 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.
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 # 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 THP is disabled.
[33mredis_1       |[0m 1:M 27 Sep 12:55:47.734 * Ready to accept connections
[36mst2-docker-gkz_stackstorm_1 exited with code 128
[0m[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=3131103a536e
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] db version v3.4.22
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] git version: aa313e18da568c4afd120f99e56d2da7d7fcdd58
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] allocator: tcmalloc
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] modules: none
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] build environment:
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten]     distarch: x86_64
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten]     target_arch: x86_64
[32mmongo_1       |[0m 2019-09-27T12:55:46.786+0000 I CONTROL  [initandlisten] options: {}
[32mmongo_1       |[0m 2019-09-27T12:55:46.789+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
[32mmongo_1       |[0m 2019-09-27T12:55:46.789+0000 I STORAGE  [initandlisten] 
[32mmongo_1       |[0m 2019-09-27T12:55:46.789+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
[32mmongo_1       |[0m 2019-09-27T12:55:46.789+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
[32mmongo_1       |[0m 2019-09-27T12:55:46.789+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=7363M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),
[32mmongo_1       |[0m 2019-09-27T12:55:46.892+0000 I STORAGE  [initandlisten] WiredTiger message [1569588946:892580][1:0x7f3ed5402d40], txn-recover: Main recovery loop: starting at 1/702336
[32mmongo_1       |[0m 2019-09-27T12:55:46.955+0000 I STORAGE  [initandlisten] WiredTiger message [1569588946:955215][1:0x7f3ed5402d40], txn-recover: Recovering log 1 through 2
[32mmongo_1       |[0m 2019-09-27T12:55:46.999+0000 I STORAGE  [initandlisten] WiredTiger message [1569588946:999508][1:0x7f3ed5402d40], txn-recover: Recovering log 2 through 2
[32mmongo_1       |[0m 2019-09-27T12:55:47.257+0000 I CONTROL  [initandlisten] 
[32mmongo_1       |[0m 2019-09-27T12:55:47.257+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
[32mmongo_1       |[0m 2019-09-27T12:55:47.257+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
[32mmongo_1       |[0m 2019-09-27T12:55:47.257+0000 I CONTROL  [initandlisten] 
[32mmongo_1       |[0m 2019-09-27T12:55:47.317+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
[32mmongo_1       |[0m 2019-09-27T12:55:47.317+0000 I NETWORK  [thread1] waiting for connections on port 27017
[32mmongo_1       |[0m 2019-09-27T12:55:51.655+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59534 #1 (1 connection now open)
[32mmongo_1       |[0m 2019-09-27T12:55:51.658+0000 I NETWORK  [conn1] received client metadata from 172.24.0.6:59534 conn1: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:51.666+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59536 #2 (2 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:51.667+0000 I NETWORK  [conn2] received client metadata from 172.24.0.6:59536 conn2: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.098+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59542 #3 (3 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.113+0000 I NETWORK  [conn3] received client metadata from 172.24.0.6:59542 conn3: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.129+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59544 #4 (4 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.130+0000 I NETWORK  [conn4] received client metadata from 172.24.0.6:59544 conn4: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.152+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59546 #5 (5 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.169+0000 I NETWORK  [conn5] received client metadata from 172.24.0.6:59546 conn5: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.177+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59548 #6 (6 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.178+0000 I NETWORK  [conn6] received client metadata from 172.24.0.6:59548 conn6: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.262+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59550 #7 (7 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.264+0000 I NETWORK  [conn7] received client metadata from 172.24.0.6:59550 conn7: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.271+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59552 #8 (8 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.272+0000 I NETWORK  [conn8] received client metadata from 172.24.0.6:59552 conn8: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.466+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59554 #9 (9 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.469+0000 I NETWORK  [conn9] received client metadata from 172.24.0.6:59554 conn9: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.478+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59556 #10 (10 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.484+0000 I NETWORK  [conn10] received client metadata from 172.24.0.6:59556 conn10: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.783+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59562 #11 (11 connections now open)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m               RabbitMQ 3.6.16. Copyright (C) 2007-2018 Pivotal Software, Inc.
[35mrabbitmq_1    |[0m   ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
[35mrabbitmq_1    |[0m   ##  ##
[35mrabbitmq_1    |[0m   ##########  Logs: tty
[35mrabbitmq_1    |[0m   ######  ##        tty
[35mrabbitmq_1    |[0m   ##########
[35mrabbitmq_1    |[0m               Starting broker...
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:55 ===
[35mrabbitmq_1    |[0m Starting RabbitMQ 3.6.16 on Erlang 19.2.1
[35mrabbitmq_1    |[0m Copyright (C) 2007-2018 Pivotal Software, Inc.
[35mrabbitmq_1    |[0m Licensed under the MPL.  See http://www.rabbitmq.com/
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:55 ===
[35mrabbitmq_1    |[0m node           : rabbit@5f40f3835c15
[35mrabbitmq_1    |[0m home dir       : /var/lib/rabbitmq
[35mrabbitmq_1    |[0m config file(s) : /etc/rabbitmq/rabbitmq.config
[35mrabbitmq_1    |[0m cookie hash    : aGV/f96QjYb6JxC7TsKmIg==
[35mrabbitmq_1    |[0m log            : tty
[35mrabbitmq_1    |[0m sasl log       : tty
[35mrabbitmq_1    |[0m database dir   : /var/lib/rabbitmq/mnesia/rabbit@5f40f3835c15
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Memory high watermark set to 6300 MiB (6606743142 bytes) of 15751 MiB (16516857856 bytes) total
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Enabling free disk space monitoring
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Disk free limit set to 50MB
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Limiting to approx 1048476 file handles (943626 sockets)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m FHC read buffering:  OFF
[35mrabbitmq_1    |[0m FHC write buffering: ON
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Database directory at /var/lib/rabbitmq/mnesia/rabbit@5f40f3835c15 is empty. Initialising from scratch...
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m     application: mnesia
[35mrabbitmq_1    |[0m     exited: stopped
[35mrabbitmq_1    |[0m     type: temporary
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Waiting for Mnesia tables for 30000 ms, 9 retries left
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Waiting for Mnesia tables for 30000 ms, 9 retries left
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Waiting for Mnesia tables for 30000 ms, 9 retries left
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Priority queues enabled, real BQ is rabbit_variable_queue
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Starting rabbit_node_monitor
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Management plugin: using rates mode 'basic'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m msg_store_transient: using rabbit_msg_store_ets_index to provide index
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m msg_store_persistent: using rabbit_msg_store_ets_index to provide index
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =WARNING REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m msg_store_persistent: rebuilding indices from scratch
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Adding vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Creating user 'admin'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Setting user tags for user 'admin' to [administrator]
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Setting permissions for 'admin' in '/' to '.*', '.*', '.*'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m started TCP Listener on [::]:5672
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Management plugin started. Port: 15672
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[32mmongo_1       |[0m 2019-09-27T12:55:52.791+0000 I NETWORK  [conn11] received client metadata from 172.24.0.6:59562 conn11: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:52.822+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59564 #12 (12 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:52.824+0000 I NETWORK  [conn12] received client metadata from 172.24.0.6:59564 conn12: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.008+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59568 #13 (13 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.009+0000 I NETWORK  [conn13] received client metadata from 172.24.0.6:59568 conn13: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.012+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59570 #14 (14 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.013+0000 I NETWORK  [conn14] received client metadata from 172.24.0.6:59570 conn14: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.043+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59572 #15 (15 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.056+0000 I NETWORK  [conn15] received client metadata from 172.24.0.6:59572 conn15: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.076+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59574 #16 (16 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.080+0000 I NETWORK  [conn16] received client metadata from 172.24.0.6:59574 conn16: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.086+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59576 #17 (17 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.086+0000 I NETWORK  [conn17] received client metadata from 172.24.0.6:59576 conn17: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.092+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59578 #18 (18 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.096+0000 I NETWORK  [conn18] received client metadata from 172.24.0.6:59578 conn18: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.453+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59586 #19 (19 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.453+0000 I NETWORK  [conn19] received client metadata from 172.24.0.6:59586 conn19: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.457+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59588 #20 (20 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.460+0000 I NETWORK  [conn20] received client metadata from 172.24.0.6:59588 conn20: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.521+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59590 #21 (21 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.533+0000 I NETWORK  [conn21] received client metadata from 172.24.0.6:59590 conn21: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.548+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59592 #22 (22 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.549+0000 I NETWORK  [conn22] received client metadata from 172.24.0.6:59592 conn22: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.644+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59600 #23 (23 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.644+0000 I NETWORK  [conn23] received client metadata from 172.24.0.6:59600 conn23: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:53.648+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59602 #24 (24 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:53.648+0000 I NETWORK  [conn24] received client metadata from 172.24.0.6:59602 conn24: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.140+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59606 #25 (25 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.141+0000 I NETWORK  [conn25] received client metadata from 172.24.0.6:59606 conn25: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.144+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59608 #26 (26 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.145+0000 I NETWORK  [conn26] received client metadata from 172.24.0.6:59608 conn26: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.209+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59610 #27 (27 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.210+0000 I NETWORK  [conn27] received client metadata from 172.24.0.6:59610 conn27: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.213+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59612 #28 (28 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.216+0000 I NETWORK  [conn28] received client metadata from 172.24.0.6:59612 conn28: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.234+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59614 #29 (29 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.236+0000 I NETWORK  [conn29] received client metadata from 172.24.0.6:59614 conn29: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[35mrabbitmq_1    |[0m Statistics database started.
[35mrabbitmq_1    |[0m  completed with 6 plugins.
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:55:57 ===
[35mrabbitmq_1    |[0m Server startup complete; 6 plugins started.
[35mrabbitmq_1    |[0m  * rabbitmq_management
[35mrabbitmq_1    |[0m  * rabbitmq_management_agent
[35mrabbitmq_1    |[0m  * rabbitmq_web_dispatch
[35mrabbitmq_1    |[0m  * cowboy
[35mrabbitmq_1    |[0m  * cowlib
[35mrabbitmq_1    |[0m  * amqp_client
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.553.0> (172.24.0.6:54750 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m connection <0.553.0> (172.24.0.6:54750 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.553.0> (172.24.0.6:54750 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.657.0> (172.24.0.6:54752 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m connection <0.657.0> (172.24.0.6:54752 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.698.0> (172.24.0.6:54754 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m connection <0.698.0> (172.24.0.6:54754 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.657.0> (172.24.0.6:54752 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.738.0> (172.24.0.6:54756 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.755.0> (172.24.0.6:54758 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m connection <0.738.0> (172.24.0.6:54756 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m connection <0.755.0> (172.24.0.6:54758 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:02 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.698.0> (172.24.0.6:54754 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.781.0> (172.24.0.6:54760 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.781.0> (172.24.0.6:54760 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.819.0> (172.24.0.6:54762 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.819.0> (172.24.0.6:54762 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.781.0> (172.24.0.6:54760 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.886.0> (172.24.0.6:54764 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.889.0> (172.24.0.6:54766 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.889.0> (172.24.0.6:54766 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.886.0> (172.24.0.6:54764 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.819.0> (172.24.0.6:54762 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.946.0> (172.24.0.6:54768 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.946.0> (172.24.0.6:54768 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.964.0> (172.24.0.6:54770 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.964.0> (172.24.0.6:54770 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.979.0> (172.24.0.6:54772 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.979.0> (172.24.0.6:54772 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.886.0> (172.24.0.6:54764 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.889.0> (172.24.0.6:54766 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1119.0> (172.24.0.6:54774 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.1119.0> (172.24.0.6:54774 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1127.0> (172.24.0.6:54776 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m connection <0.1127.0> (172.24.0.6:54776 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:03 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.946.0> (172.24.0.6:54768 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.964.0> (172.24.0.6:54770 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.979.0> (172.24.0.6:54772 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1177.0> (172.24.0.6:54778 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1177.0> (172.24.0.6:54778 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1127.0> (172.24.0.6:54776 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1280.0> (172.24.0.6:54782 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1280.0> (172.24.0.6:54782 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1309.0> (172.24.0.6:54784 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1309.0> (172.24.0.6:54784 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1332.0> (172.24.0.6:54788 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1346.0> (172.24.0.6:54790 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1365.0> (172.24.0.6:54792 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1346.0> (172.24.0.6:54790 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1332.0> (172.24.0.6:54788 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1365.0> (172.24.0.6:54792 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1433.0> (172.24.0.6:54794 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1280.0> (172.24.0.6:54782 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m connection <0.1433.0> (172.24.0.6:54794 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1309.0> (172.24.0.6:54784 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1365.0> (172.24.0.6:54792 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1568.0> (172.24.0.6:54796 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:04 ===
[32mmongo_1       |[0m 2019-09-27T12:55:54.268+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59616 #30 (30 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.286+0000 I NETWORK  [conn30] received client metadata from 172.24.0.6:59616 conn30: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.296+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59618 #31 (31 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.296+0000 I NETWORK  [conn31] received client metadata from 172.24.0.6:59618 conn31: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.324+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59620 #32 (32 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.325+0000 I NETWORK  [conn32] received client metadata from 172.24.0.6:59620 conn32: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.443+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59622 #33 (33 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.445+0000 I NETWORK  [conn33] received client metadata from 172.24.0.6:59622 conn33: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.450+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59624 #34 (34 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.452+0000 I NETWORK  [conn34] received client metadata from 172.24.0.6:59624 conn34: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.585+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59632 #35 (35 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.586+0000 I NETWORK  [conn35] received client metadata from 172.24.0.6:59632 conn35: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.589+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59634 #36 (36 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.589+0000 I NETWORK  [conn36] received client metadata from 172.24.0.6:59634 conn36: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.803+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59642 #37 (37 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.804+0000 I NETWORK  [conn37] received client metadata from 172.24.0.6:59642 conn37: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:55:54.806+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59644 #38 (38 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:55:54.806+0000 I NETWORK  [conn38] received client metadata from 172.24.0.6:59644 conn38: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:56:08.900+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59730 #39 (39 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:56:08.902+0000 I NETWORK  [conn39] received client metadata from 172.24.0.6:59730 conn39: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:56:08.907+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59732 #40 (40 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:56:08.908+0000 I NETWORK  [conn40] received client metadata from 172.24.0.6:59732 conn40: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[32mmongo_1       |[0m 2019-09-27T12:56:11.545+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59750 #41 (41 connections now open)
[32mmongo_1       |[0m 2019-09-27T12:56:11.650+0000 I NETWORK  [conn41] received client metadata from 172.24.0.6:59750 conn41: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }
[35mrabbitmq_1    |[0m connection <0.1568.0> (172.24.0.6:54796 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1590.0> (172.24.0.6:54798 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m connection <0.1590.0> (172.24.0.6:54798 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1346.0> (172.24.0.6:54790 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1332.0> (172.24.0.6:54788 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1433.0> (172.24.0.6:54794 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m closing AMQP connection <0.1568.0> (172.24.0.6:54796 -> 172.24.0.2:5672, vhost: '/', user: 'admin')
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1689.0> (172.24.0.6:54802 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:05 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1692.0> (172.24.0.6:54804 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m Connection <0.1692.0> (172.24.0.6:54804 -> 172.24.0.2:5672) has a client-provided name: mistral-server:391:f5fe329a-e4de-4b2a-98a1-ebd25a474329
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m Connection <0.1689.0> (172.24.0.6:54802 -> 172.24.0.2:5672) has a client-provided name: mistral-server:391:b116822a-1195-424b-9e82-271d5b340afd
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m connection <0.1692.0> (172.24.0.6:54804 -> 172.24.0.2:5672 - mistral-server:391:f5fe329a-e4de-4b2a-98a1-ebd25a474329): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m connection <0.1689.0> (172.24.0.6:54802 -> 172.24.0.2:5672 - mistral-server:391:b116822a-1195-424b-9e82-271d5b340afd): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1711.0> (172.24.0.6:54806 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m Connection <0.1711.0> (172.24.0.6:54806 -> 172.24.0.2:5672) has a client-provided name: mistral-server:391:c39c2953-063d-425b-b638-54373ec27fab
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:06 ===
[35mrabbitmq_1    |[0m connection <0.1711.0> (172.24.0.6:54806 -> 172.24.0.2:5672 - mistral-server:391:c39c2953-063d-425b-b638-54373ec27fab): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:07 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1771.0> (172.24.0.6:54810 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:07 ===
[35mrabbitmq_1    |[0m connection <0.1771.0> (172.24.0.6:54810 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1792.0> (172.24.0.6:54814 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1795.0> (172.24.0.6:54816 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1792.0> (172.24.0.6:54814 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1795.0> (172.24.0.6:54816 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1815.0> (172.24.0.6:54818 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1818.0> (172.24.0.6:54820 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1815.0> (172.24.0.6:54818 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1818.0> (172.24.0.6:54820 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1841.0> (172.24.0.6:54822 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1841.0> (172.24.0.6:54822 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1854.0> (172.24.0.6:54824 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m connection <0.1854.0> (172.24.0.6:54824 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:08 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1867.0> (172.24.0.6:54830 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1867.0> (172.24.0.6:54830 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1880.0> (172.24.0.6:54832 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1880.0> (172.24.0.6:54832 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1885.0> (172.24.0.6:54834 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1885.0> (172.24.0.6:54834 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1906.0> (172.24.0.6:54836 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1906.0> (172.24.0.6:54836 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1916.0> (172.24.0.6:54838 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1919.0> (172.24.0.6:54840 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1916.0> (172.24.0.6:54838 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1919.0> (172.24.0.6:54840 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1943.0> (172.24.0.6:54842 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:09 ===
[35mrabbitmq_1    |[0m connection <0.1943.0> (172.24.0.6:54842 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:11 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1957.0> (172.24.0.6:54844 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:11 ===
[35mrabbitmq_1    |[0m connection <0.1957.0> (172.24.0.6:54844 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:11 ===
[35mrabbitmq_1    |[0m accepting AMQP connection <0.1971.0> (172.24.0.6:54850 -> 172.24.0.2:5672)
[35mrabbitmq_1    |[0m 
[35mrabbitmq_1    |[0m =INFO REPORT==== 27-Sep-2019::12:56:11 ===
[35mrabbitmq_1    |[0m connection <0.1971.0> (172.24.0.6:54850 -> 172.24.0.2:5672): user 'admin' authenticated and granted access to vhost '/'
[31mpostgres_1    |[0m LOG:  database system was interrupted; last known up at 2019-09-27 11:51:42 UTC
[31mpostgres_1    |[0m LOG:  database system was not properly shut down; automatic recovery in progress
[31mpostgres_1    |[0m LOG:  redo starts at 0/14EEDE8
[31mpostgres_1    |[0m LOG:  invalid record length at 0/16C3558: wanted 24, got 0
[31mpostgres_1    |[0m LOG:  redo done at 0/16C3508
[31mpostgres_1    |[0m LOG:  last completed transaction was at log time 2019-09-27 11:51:52.424187+00
[31mpostgres_1    |[0m LOG:  MultiXact member wraparound protections are now enabled
[31mpostgres_1    |[0m LOG:  autovacuum launcher started
[31mpostgres_1    |[0m LOG:  database system is ready to accept connections
[32mmongo_1       |[0m 2019-09-27T13:00:08.512+0000 I NETWORK  [thread1] connection accepted from 172.24.0.6:59828 #42 (42 connections now open)
[32mmongo_1       |[0m 2019-09-27T13:00:08.513+0000 I NETWORK  [conn42] received client metadata from 172.24.0.6:59828 conn42: { driver: { name: "PyMongo", version: "3.7.2" }, os: { type: "Linux", name: "Ubuntu 14.04 trusty", architecture: "x86_64", version: "5.0.0-29-generic" }, platform: "CPython 2.7.6.final.0" }

```