Cannot start service mongo: network not found

[glaulom]

Hi, after installation and botfront init I try to run botfront up but can't make it work. I've got the following :

My config is :

• nodejs version: "2.2.36
• os: Linux x64 4.18.0-25-generic
• Node.js v8.16.0
• mongodb-core: 2.1.20

When running botfront logs here is what I've got

`Attaching to botfront-actions, botfront-duckling, botfront-mongo
botfront-actions | 2019-07-24 14:37:53 INFO rasa_sdk.endpoint - Starting action endpoint server...
botfront-actions | 2019-07-24 14:37:53 INFO rasa_sdk.executor - Registered function for 'action_botfront_mapping'.
botfront-actions | 2019-07-24 14:37:53 INFO rasa_sdk.executor - Registered function for 'action_botfront_mapping_follow_up'.
botfront-actions | 2019-07-24 14:37:53 INFO rasa_sdk.executor - Registered function for 'action_my_action'.
botfront-actions | 2019-07-24 14:37:53 INFO rasa_sdk.endpoint - Action endpoint is up and running. on ('0.0.0.0', 5055)
botfront-duckling | no port specified, defaulting to port 8000
botfront-duckling | Listening on http://0.0.0.0:8000
botfront-mongo | 2019-07-23T13:54:09.947+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=61176b7dd992
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] db version v4.0.9
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] git version: fc525e2d9b0e4bceff5c2201457e564362909765
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] allocator: tcmalloc
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] modules: none
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] build environment:
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] distmod: ubuntu1604
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] distarch: x86_64
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] target_arch: x86_64
botfront-mongo | 2019-07-23T13:54:09.965+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true } }
botfront-mongo | 2019-07-23T13:54:09.972+0000 I STORAGE [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
botfront-mongo | 2019-07-23T13:54:09.972+0000 I STORAGE [initandlisten]
botfront-mongo | 2019-07-23T13:54:09.972+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
botfront-mongo | 2019-07-23T13:54:09.972+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
botfront-mongo | 2019-07-23T13:54:09.972+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=2468M,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),statistics_log=(wait=0),verbose=(recovery_progress),
botfront-mongo | 2019-07-23T13:54:11.399+0000 I STORAGE [initandlisten] WiredTiger message [1563890051:399813][1:0x7f6a92073a80], txn-recover: Main recovery loop: starting at 2/6912 to 3/256
botfront-mongo | 2019-07-23T13:54:11.534+0000 I STORAGE [initandlisten] WiredTiger message [1563890051:534844][1:0x7f6a92073a80], txn-recover: Recovering log 2 through 3
botfront-mongo | 2019-07-23T13:54:11.618+0000 I STORAGE [initandlisten] WiredTiger message [1563890051:618797][1:0x7f6a92073a80], txn-recover: Recovering log 3 through 3
botfront-mongo | 2019-07-23T13:54:11.686+0000 I STORAGE [initandlisten] WiredTiger message [1563890051:686754][1:0x7f6a92073a80], txn-recover: Set global recovery timestamp: 0
botfront-mongo | 2019-07-23T13:54:11.752+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
botfront-mongo | 2019-07-23T13:54:11.831+0000 I CONTROL [initandlisten]
botfront-mongo | 2019-07-23T13:54:11.832+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
botfront-mongo | 2019-07-23T13:54:11.832+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
botfront-mongo | 2019-07-23T13:54:11.832+0000 I CONTROL [initandlisten]
botfront-mongo | 2019-07-23T13:54:12.006+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
botfront-mongo | 2019-07-23T13:54:12.010+0000 I NETWORK [initandlisten] waiting for connections on port 27017
botfront-mongo | 2019-07-23T13:54:12.924+0000 I NETWORK [listener] connection accepted from 172.21.0.6:45568 #1 (1 connection now open)
botfront-mongo | 2019-07-23T13:54:12.936+0000 I NETWORK [conn1] received client metadata from 172.21.0.6:45568 conn1: { driver: { name: "nodejs", version: "3.0.7" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 3.0.7" }
botfront-mongo | 2019-07-23T13:54:12.947+0000 I NETWORK [conn1] end connection 172.21.0.6:45568 (0 connections now open)
botfront-mongo | 2019-07-23T13:54:14.050+0000 I NETWORK [listener] connection accepted from 172.21.0.6:45574 #2 (1 connection now open)
botfront-mongo | 2019-07-23T13:54:14.059+0000 I NETWORK [conn2] received client metadata from 172.21.0.6:45574 conn2: { driver: { name: "nodejs", version: "3.1.13" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 3.1.11" }
botfront-mongo | 2019-07-23T13:54:14.132+0000 I NETWORK [listener] connection accepted from 172.21.0.5:34300 #3 (2 connections now open)
botfront-mongo | 2019-07-23T13:54:14.132+0000 I NETWORK [listener] connection accepted from 172.21.0.5:34302 #4 (3 connections now open)
botfront-mongo | 2019-07-23T13:54:14.133+0000 I NETWORK [listener] connection accepted from 172.21.0.5:34304 #5 (4 connections now open)
botfront-mongo | 2019-07-23T13:54:14.185+0000 I NETWORK [listener] connection accepted from 172.21.0.5:34306 #6 (5 connections now open)
botfront-mongo | 2019-07-23T13:54:14.195+0000 I NETWORK [conn3] received client metadata from 172.21.0.5:34300 conn3: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 2.1.20" }
botfront-mongo | 2019-07-23T13:54:14.196+0000 I NETWORK [conn4] received client metadata from 172.21.0.5:34302 conn4: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 2.1.20" }
botfront-mongo | 2019-07-23T13:54:14.197+0000 I NETWORK [conn5] received client metadata from 172.21.0.5:34304 conn5: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 2.1.20" }
botfront-mongo | 2019-07-23T13:54:14.217+0000 I NETWORK [conn6] received client metadata from 172.21.0.5:34306 conn6: { driver: { name: "nodejs", version: "3.1.13" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.18.0-25-generic" }, platform: "Node.js v8.16.0, LE, mongodb-core: 3.1.11" }
botfront-mongo | 2019-07-23T13:55:34.939+0000 I NETWORK [conn6] end connection 172.21.0.5:34306 (4 connections now open)
botfront-mongo | 2019-07-23T13:55:34.939+0000 I NETWORK [conn3] end connection 172.21.0.5:34300 (3 connections now open)
botfront-mongo | 2019-07-23T13:55:34.939+0000 I NETWORK [conn4] end connection 172.21.0.5:34302 (2 connections now open)
botfront-mongo | 2019-07-23T13:55:34.939+0000 I NETWORK [conn5] end connection 172.21.0.5:34304 (1 connection now open)
botfront-mongo | 2019-07-23T13:55:34.983+0000 I CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
botfront-mongo | 2019-07-23T13:55:34.984+0000 I NETWORK [signalProcessingThread] shutdown: going to close listening sockets...
botfront-mongo | 2019-07-23T13:55:34.984+0000 I NETWORK [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
botfront-mongo | 2019-07-23T13:55:34.990+0000 I CONTROL [signalProcessingThread] Shutting down free monitoring
botfront-mongo | 2019-07-23T13:55:34.990+0000 I FTDC [signalProcessingThread] Shutting down full-time diagnostic data capture
botfront-mongo | 2019-07-23T13:55:35.200+0000 I STORAGE [signalProcessingThread] WiredTigerKVEngine shutting down
botfront-mongo | 2019-07-23T13:55:35.200+0000 I STORAGE [signalProcessingThread] Shutting down session sweeper thread
botfront-mongo | 2019-07-23T13:55:35.200+0000 I STORAGE [signalProcessingThread] Finished shutting down session sweeper thread
botfront-mongo | 2019-07-23T13:55:36.375+0000 I STORAGE [signalProcessingThread] shutdown: removing fs lock...
botfront-mongo | 2019-07-23T13:55:36.375+0000 I CONTROL [signalProcessingThread] now exiting
botfront-mongo | 2019-07-23T13:55:36.375+0000 I CONTROL [signalProcessingThread] shutting down with code:0

`

[wglambert]

The logs only show [signalProcessingThread] got signal 15 (Terminated) which is SIGTERM. So maybe a docker stop was sent.

Since this looks like an issue with your setup/environment I'd recommend asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow