Docker + MongoDB：如何使用RoboMongo查看數據庫？

Question

如何使用RoboMongo或類似方法訪問Docker創建的mongo數據庫？

在使用Doncker之前，我已經將mongodb安裝到了我的Linux機器中。 所以我不能在docker-compse.yml中使用端口“ 27017：27017”。 我使用“ 27018：27018”：

version: "2"
services:
  web:
    build: .
    ports:
      - "3000:3000"
    links:
      - mongo
  mongo:
    image: mongo
    volumes:
      - /data/mongodb/db:/data/db
    ports:
      - "27018:27018"

我可以使用RoboMongo來查看我在docker之前的mongo中創建的所有數據庫。 但是我如何訪問Docker的呢？

這是我的DockerFile：

FROM mhart/alpine-node:latest
ADD package.json /tmp/package.json
RUN cd /tmp && npm install
RUN mkdir -p /opt/app && cp -a /tmp/node_modules /opt/app/

WORKDIR /opt/app
ADD . /opt/app

EXPOSE 3000

CMD ["npm", "start"]

編輯：

當我在終端上運行docker時：

$ docker-compose up
Starting dummyapp_mongo_1
Recreating dummyapp_web_1
Attaching to dummyapp_mongo_1, dummyapp_web_1
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=571498710dc0
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] db version v3.4.1
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] modules: none
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] build environment:
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten]     distmod: debian81
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongo_1  | 2017-01-03T10:20:35.083+0000 I CONTROL  [initandlisten] options: {}
mongo_1  | 2017-01-03T10:20:35.104+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
mongo_1  | 2017-01-03T10:20:35.104+0000 I STORAGE  [initandlisten] 
mongo_1  | 2017-01-03T10:20:35.104+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongo_1  | 2017-01-03T10:20:35.104+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongo_1  | 2017-01-03T10:20:35.104+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1454M,session_max=20000,eviction=(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),
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] 
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] 
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] 
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] 
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
mongo_1  | 2017-01-03T10:20:36.385+0000 I CONTROL  [initandlisten] 
mongo_1  | 2017-01-03T10:20:36.389+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
mongo_1  | 2017-01-03T10:20:36.390+0000 I NETWORK  [thread1] waiting for connections on port 27017
web_1    | 
web_1    | > dummy-app@0.0.0 start /opt/app
web_1    | > node ./bin/www

編輯2：

當我在GET http：// localhost：3000 / data / from / db或POST http：// localhost：3000 / data / into / db上時，將端口更改為“ 27018：27017”后，出現以下新錯誤：

failed to connect to server [mongo:27017] on first connect

MongoError: failed to connect to server [mongo:27017] on first connect
    at Pool.<anonymous> (/opt/app/node_modules/mongodb-core/lib/topologies/server.js:325:35)
    at emitOne (events.js:96:13)
    at Pool.emit (events.js:188:7)
    at Connection.<anonymous> (/opt/app/node_modules/mongodb-core/lib/connection/pool.js:270:12)
    at Connection.g (events.js:292:16)
    at emitTwo (events.js:106:13)
    at Connection.emit (events.js:191:7)
    at Socket.<anonymous> (/opt/app/node_modules/mongodb-core/lib/connection/connection.js:173:49)
    at Socket.g (events.js:292:16)
    at emitOne (events.js:96:13)

有什么想法嗎？

Answer 1

您確定您的mongodb監聽容器中的端口27018嗎？ 僅基於您帖子中的信息，我猜測mongodb在容器中監聽其默認端口27017，並且您正在將主機27018映射到mongo不在監聽的容器27018。 該ports項應類似於： 27018:27017以便主機上未使用的端口27018映射到容器上的正確端口27017。

此暴露與npm容器無關，因為它使用不同的機制來暴露端口，並在容器之間建立鏈接。 您會發現，如果將其他mongodb客戶端放入容器中，則鏈接也將對其起作用。 但是要與主機進行交互，您需要將容器中的正確端口公開給主機上的可用端口。

https://docs.docker.com/compose/compose-file/#/ports