docker - ./conf.js:/app/conf.js vs. zenbot conf.js conflict

[ricroc]

Please go to Stack Overflow for help and support:

https://stackoverflow.com/questions/tagged/zenbot

If you open a GitHub issue, here is our policy:

1. It must be a bug or a feature request.
2. The form below must be filled out.

Here's why we have that policy: Zenbot developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies hundreds of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

---

System information

• Have I written custom code (as opposed to using zenbot vanilla): no
• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows
• Zenbot version: 4
• NodeJS version: 8.9.3
• Python version:
• Exact command to reproduce:

Describe the problem

I was able to install and run zenbot with mongdb and docker in windows. no where to add API keys due to conflicting conf.js files between mongodb and zenbot

Source code / logs

Running on windows

C:\Users\Ric Rocamora\OneDrive\Crypto\zenbot>docker-compose up
Starting zenbot_mongodb-data_1 ...
Starting zenbot_mongodb-data_1 ... done
Starting zenbot_mongodb_1 ...
Starting zenbot_mongodb_1 ... done
Starting zenbot_server_1 ...
Starting zenbot_server_1 ... done
Attaching to zenbot_mongodb-data_1, zenbot_mongodb_1, zenbot_server_1
mongodb_1       | 2017-12-20T11:38:16.248+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=1bf007ed942d
mongodb_1       | 2017-12-20T11:38:16.248+0000 I CONTROL  [initandlisten] db version v3.6.0
mongodb_1       | 2017-12-20T11:38:16.248+0000 I CONTROL  [initandlisten] git version: a57d8e71e6998a2d0afde7edc11bd23e5661c915
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten] modules: none
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten] build environment:
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten]     distmod: debian81
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongodb_1       | 2017-12-20T11:38:16.249+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true }, storage: { mmapv1: { smallFiles: true } } }
mongodb_1       | 2017-12-20T11:38:16.249+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
mongodb_1       | 2017-12-20T11:38:16.249+0000 I STORAGE  [initandlisten]
mongodb_1       | 2017-12-20T11:38:16.249+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongodb_1       | 2017-12-20T11:38:16.249+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongodb_1       | 2017-12-20T11:38:16.249+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=478M,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),
mongodb_1       | 2017-12-20T11:38:16.401+0000 I STORAGE  [initandlisten] WiredTiger message [1513769896:401495][1:0x7f24186fea00], txn-recover: Main recovery loop: starting at 2/355328
mongodb_1       | 2017-12-20T11:38:16.485+0000 I STORAGE  [initandlisten] WiredTiger message [1513769896:485517][1:0x7f24186fea00], txn-recover: Recovering log 2 through 3
mongodb_1       | 2017-12-20T11:38:16.539+0000 I STORAGE  [initandlisten] WiredTiger message [1513769896:539380][1:0x7f24186fea00], txn-recover: Recovering log 3 through 3
mongodb_1       | 2017-12-20T11:38:16.632+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
mongodb_1       | 2017-12-20T11:38:16.632+0000 I CONTROL  [initandlisten]
mongodb_1       | 2017-12-20T11:38:16.632+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1       | 2017-12-20T11:38:16.632+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongodb_1       | 2017-12-20T11:38:16.632+0000 I CONTROL  [initandlisten]
mongodb_1       | 2017-12-20T11:38:16.642+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
mongodb_1       | 2017-12-20T11:38:16.642+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
zenbot_mongodb-data_1 exited with code 0
mongodb_1       | 2017-12-20T11:38:17.472+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36756 #1 (1 connection now open)
mongodb_1       | 2017-12-20T11:38:17.477+0000 I NETWORK  [conn1] received client metadata from 172.17.0.2:36756 conn: { driver: { name: "nodejs", version: "2.2.33" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.9.49-moby" }, platform: "Node.js v8.9.3, LE, mongodb-core: 2.1.17" }
server_1        | node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
server_1        | In the future, you will have to enable it yourself.
server_1        | See https://github.com/yagop/node-telegram-bot-api/issues/319. module.js:635:30
server_1        | fetching pre-roll data:
server_1        | api running on 172.17.0.2:20069/trades
mongodb_1       | 2017-12-20T11:38:18.460+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36758 #2 (2 connections now open)
mongodb_1       | 2017-12-20T11:38:18.632+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36760 #3 (3 connections now open)
mongodb_1       | 2017-12-20T11:38:18.639+0000 I NETWORK  [conn3] received client metadata from 172.17.0.2:36760 conn: { driver: { name: "nodejs", version: "2.2.33" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.9.49-moby" }, platform: "Node.js v8.9.3, LE, mongodb-core: 2.1.17" }
server_1        | Wed, 20 Dec 2017 11:38:19 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
server_1        | In the future, you will have to enable it yourself.
server_1        | See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:635:30
mongodb_1       | 2017-12-20T11:38:19.483+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36762 #4 (4 connections now open)
mongodb_1       | 2017-12-20T11:38:19.894+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36766 #5 (5 connections now open)
mongodb_1       | 2017-12-20T11:38:19.897+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36768 #6 (6 connections now open)
mongodb_1       | 2017-12-20T11:38:19.899+0000 I NETWORK  [listener] connection accepted from 172.17.0.2:36770 #7 (7 connections now open)
server_1        |
server_1        | skipping 0 hrs of previously collected data
server_1        |
server_1        | gdax.BTC-USD saved 100 trades 1 days left

C:\Users\Ric Rocamora\OneDrive\Crypto\zenbot>docker-compose up -d
Starting zenbot_mongodb-data_1 ...
Starting zenbot_mongodb-data_1 ... done
Starting zenbot_mongodb_1 ...
Starting zenbot_mongodb_1 ... done
Starting zenbot_server_1 ...
Starting zenbot_server_1 ... done

C:\Users\Ric Rocamora\OneDrive\Crypto\zenbot>

all is well but... i cannot add the API keys to the exchanges.

I am unable to copy the conf-sample.js to conf.js because it seems the installation created a conf.js folder which cannot be removed.

if attempted;

C:\Users\Ric Rocamora\OneDrive\Crypto\zenbot>docker-compose up -d
Creating zenbot_mongodb-data_1 ...
Creating zenbot_mongodb-data_1 ... done
Creating zenbot_mongodb_1 ...
Creating zenbot_mongodb_1 ... done
Creating zenbot_server_1 ...
Creating zenbot_server_1 ... error

ERROR: for zenbot_server_1  Cannot start service server: Cannot link to a non running container: /zenbot_mongodb_1 AS /zenbot_server_1/zenbot_mongodb_1

ERROR: for server  Cannot start service server: Cannot link to a non running container: /zenbot_mongodb_1 AS /zenbot_server_1/zenbot_mongodb_1
ERROR: Encountered errors while bringing up the project.

if i create the conf.js file from the sample;

ERROR: for zenbot_server_1  Cannot start service server: oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:368: container init caused \"rootfs_linux.go:57: mounting \\\"/C/Users/Ric Rocamora/OneDrive/Crypto/zenbot/conf.js\\\" to rootfs \\\"/var/lib/docker/overlay2/9efffb863deb0a67fc9a364bcd4bd08a75a984c2a08206dc3dd3c75b9be744d1/merged\\\" at \\\"/var/lib/docker/overlay2/9efffb863deb0a67fc9a364bcd4bd08a75a984c2a08206dc3dd3c75b9be744d1/merged/app/conf.js\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for server  Cannot start service server: oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:368: container init caused \"rootfs_linux.go:57: mounting \\\"/C/Users/Ric Rocamora/OneDrive/Crypto/zenbot/conf.js\\\" to rootfs \\\"/var/lib/docker/overlay2/9efffb863deb0a67fc9a364bcd4bd08a75a984c2a08206dc3dd3c75b9be744d1/merged\\\" at \\\"/var/lib/docker/overlay2/9efffb863deb0a67fc9a364bcd4bd08a75a984c2a08206dc3dd3c75b9be744d1/merged/app/conf.js\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

returning the empty conf.js folder allows zenbot to start with the docker and mongodb but unable to add api keys

[mrzobot]

I have same issue, just posted that as an issue.

[DeviaVir]

Dear issue reporter,

We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.

You can find it here: https://reddit.com/r/zenbot

This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.

Thanks for contributing time and effort!

Greetings,
🤖