如何使用默認集合和數據創建Mongo Docker Image？

Question

我需要支持在這裏建立我自己的mongo泊塢窗圖像。

我有一個腳本列表，用於創建數據並將數據插入到MongoDB中，該數據將在我的Dockerfile中調用，以提供具有默認集合和數據的泊塢窗圖像。

這裏是我的Dockerfile看起來像目前：

FROM mongo:latest 

RUN mkdir -p /data/scripts 

COPY . /data/scripts 

RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db/ 

RUN FILES=scripts/*-create.js 
RUN for f in $FILES; do mongo mydb $f; done 

RUN FILES=scripts/*-insert.js 
RUN for f in $FILES; do mongo mydb $f; done 

RUN mongod --shutdown 

我嘗試了不同的選項來啓動和停止的mongod始終的兩個故障之一，目前腳本引發以下錯誤：

There doesn't seem to be a server running with dbpath: /data/db 

更新

@馬特的答案後，我可以成功運行的命令鏈，但仍無法š ee我的數據庫（稱爲my-db），那裏的集合和數據。

目前Dockerfile：

FROM mongo:latest 

RUN mkdir -p /data/db/scripts 

COPY . /data/db 

RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db \ 
    && CREATE_FILES=/data/db/scripts/*-create.js \ 
    && for f in $CREATE_FILES; do mongo 127.0.0.1:27017 $f; done \ 
    && INSERT_FILES=/data/db/scripts/*-insert.js \ 
    && for f in $INSERT_FILES; do mongo 127.0.0.1:27017 $f; done \ 
    && mongod --shutdown 

從泊塢窗構建命令的輸出：

Sending build context to Docker daemon 10.24 kB 
Step 1 : FROM mongo:latest 
---> c08c92f4cb13 
Step 2 : RUN mkdir -p /data/db/scripts 
---> Running in a7088943bb57 
---> 373c7319927d 
Removing intermediate container a7088943bb57 
Step 3 : COPY . /data/db 
---> 8fa84884edb7 
Removing intermediate container ae43e2c24fee 
Step 4 : RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db  && CREATE_FILES=/data/db/scripts/*-create.js && for f in $CREATE_FILES; do mongo 127.0.0.1:27017 $f; done && INSERT_FILES=/data/db/scripts/*-insert.js && for f in $INSERT_FILES; do mongo 127.0.0.1:27017 $f; done && mongod --shutdown 
---> Running in 33970b6865ee 
about to fork child process, waiting until server is ready for connections. 
forked process: 10 
child process started successfully, parent exiting 
MongoDB shell version: 3.0.7 
connecting to: 127.0.0.1:27017/test 
MongoDB shell version: 3.0.7 
connecting to: 127.0.0.1:27017/test 
killing process with pid: 10 
---> 8451e43b7749 
Removing intermediate container 33970b6865ee 
Successfully built 8451e43b7749 

但正如我所說，我仍然看不到我的數據庫的數據庫，集合和數據使用mongo shell。 我也連接到正在運行的容器，並得到了mongodb.log：

2015-11-06T16:15:14.562+0000 I JOURNAL [initandlisten] journal dir=/data/db/journal 
2015-11-06T16:15:14.562+0000 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed 
2015-11-06T16:15:14.698+0000 I JOURNAL [initandlisten] preallocateIsFaster=true 2.36 
2015-11-06T16:15:14.746+0000 I JOURNAL [durability] Durability thread started 
2015-11-06T16:15:14.746+0000 I JOURNAL [journal writer] Journal writer thread started 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] MongoDB starting : pid=10 port=27017 dbpath=/data/db 64-bit host=9c05d483673a 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended. 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'. 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] **  We suggest setting it to 'never' 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'. 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] **  We suggest setting it to 'never' 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] db version v3.0.7 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] git version: 6ce7cbe8c6b899552dadd907604559806aa2e9bd 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] build info: Linux ip-10-183-78-195 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 BOOST_LIB_VERSION=1_49 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] allocator: tcmalloc 
2015-11-06T16:15:14.747+0000 I CONTROL [initandlisten] options: { processManagement: { fork: true }, storage: { dbPath: "/data/db" }, systemLog: { destination: "file", path: "/var/log/mongodb.log" } } 
2015-11-06T16:15:14.748+0000 I INDEX [initandlisten] allocating new ns file /data/db/local.ns, filling with zeroes... 
2015-11-06T16:15:14.802+0000 I STORAGE [FileAllocator] allocating new datafile /data/db/local.0, filling with zeroes... 
2015-11-06T16:15:14.802+0000 I STORAGE [FileAllocator] creating directory /data/db/_tmp 
2015-11-06T16:15:14.804+0000 I STORAGE [FileAllocator] done allocating datafile /data/db/local.0, size: 64MB, took 0 secs 
2015-11-06T16:15:14.807+0000 I NETWORK [initandlisten] waiting for connections on port 27017 
2015-11-06T16:15:14.830+0000 I NETWORK [initandlisten] connection accepted from 127.0.0.1:49641 #1 (1 connection now open) 
2015-11-06T16:15:14.832+0000 I INDEX [conn1] allocating new ns file /data/db/my-db.ns, filling with zeroes... 
2015-11-06T16:15:14.897+0000 I STORAGE [FileAllocator] allocating new datafile /data/db/my-db.0, filling with zeroes... 
2015-11-06T16:15:14.898+0000 I STORAGE [FileAllocator] done allocating datafile /data/db/my-db.0, size: 64MB, took 0 secs 
2015-11-06T16:15:14.904+0000 I NETWORK [conn1] end connection 127.0.0.1:49641 (0 connections now open) 
2015-11-06T16:15:14.945+0000 I NETWORK [initandlisten] connection accepted from 127.0.0.1:49642 #2 (1 connection now open) 
2015-11-06T16:15:14.958+0000 I NETWORK [conn2] end connection 127.0.0.1:49642 (0 connections now open) 
2015-11-06T16:15:14.982+0000 I CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends 
2015-11-06T16:15:14.982+0000 I CONTROL [signalProcessingThread] now exiting 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] shutdown: going to close listening sockets... 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] closing listening socket: 6 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] closing listening socket: 7 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] shutdown: going to flush diaglog... 
2015-11-06T16:15:14.982+0000 I NETWORK [signalProcessingThread] shutdown: going to close sockets... 
2015-11-06T16:15:14.982+0000 I STORAGE [signalProcessingThread] shutdown: waiting for fs preallocator... 
2015-11-06T16:15:14.982+0000 I STORAGE [signalProcessingThread] shutdown: final commit... 
2015-11-06T16:15:15.008+0000 I JOURNAL [signalProcessingThread] journalCleanup... 
2015-11-06T16:15:15.008+0000 I JOURNAL [signalProcessingThread] removeJournalFiles 
2015-11-06T16:15:15.009+0000 I JOURNAL [signalProcessingThread] Terminating durability thread ... 
2015-11-06T16:15:15.088+0000 I JOURNAL [journal writer] Journal writer thread stopped 
2015-11-06T16:15:15.088+0000 I JOURNAL [durability] Durability thread stopped 
2015-11-06T16:15:15.088+0000 I STORAGE [signalProcessingThread] shutdown: closing all files... 
2015-11-06T16:15:15.090+0000 I STORAGE [signalProcessingThread] closeAllFiles() finished 
2015-11-06T16:15:15.090+0000 I STORAGE [signalProcessingThread] shutdown: removing fs lock... 
2015-11-06T16:15:15.090+0000 I CONTROL [signalProcessingThread] dbexit: rc: 0 

我還檢查了文件夾/數據/ DB內容：

root@fbaf17233182:/data/db# ls -al 
total 16 
drwxr-xr-x 3 mongodb mongodb 4096 Nov 6 16:15 . 
drwxr-xr-x 4 root root 4096 Nov 6 16:15 .. 
drwxr-xr-x 2 root root 4096 Nov 5 18:55 scripts 

可能會有幫助：

• Parent Dockerfile
• 父Dockerfile ENTRYPOINT

Answer 1

問題是信息無法保存在/db/data上，所以我創建了一個創建我自己的數據目錄的解決方案。

# Parent Dockerfile https://github.com/docker-library/mongo/blob/982328582c74dd2f0a9c8c77b84006f291f974c3/3.0/Dockerfile 
FROM mongo:latest 

# Modify child mongo to use /data/db2 as dbpath (because /data/db wont persist the build) 
RUN mkdir -p /data/db2 \ 
    && echo "dbpath = /data/db2" > /etc/mongodb.conf \ 
    && chown -R mongodb:mongodb /data/db2 

COPY . /data/db2 

RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db2 --smallfiles \ 
    && CREATE_FILES=/data/db2/scripts/*-create.js \ 
    && for f in $CREATE_FILES; do mongo 127.0.0.1:27017 $f; done \ 
    && INSERT_FILES=/data/db2/scripts/*-insert.js \ 
    && for f in $INSERT_FILES; do mongo 127.0.0.1:27017 $f; done \ 
    && mongod --dbpath /data/db2 --shutdown \ 
    && chown -R mongodb /data/db2 

# Make the new dir a VOLUME to persists it 
VOLUME /data/db2 

CMD ["mongod", "--config", "/etc/mongodb.conf", "--smallfiles"] 

由於從docker-library/mongo Github上項目@yosifkit指出這卷將在數據存儲所產生的圖像上。我錯過了文檔。

Answer 2

在Docker鏡像構建期間，每個構建命令（如RUN）都會在其自己的Docker容器中啓動，然後在命令完成時將數據提交爲圖像。如果您在構建時運行dockviz images --tree，您將會明白。

在你的情況下，mongod在你需要它之​​前已經開始和停止了很久。你需要啓動mongo並在一個RUN步驟中運行你的腳本。您可以通過使用啓動mongod並插入數據的shell腳本來實現此目的。

你Dockerfile將運行：

RUN mongo_create_insert.sh 

然後mongo_create_insert.sh包含所有蒙戈相關步驟：

#!/usr/bin/env bash 

mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db/ 

FILES=scripts/*-create.js 
for f in $FILES; do mongo mydb $f; done 

FILES=scripts/*-insert.js 
for f in $FILES; do mongo mydb $f; done 

mongod --shutdown 

作爲一個方面說明，我傾向於在我的基本映像安裝Ansible並用它來在單個RUN命令中提供Docker鏡像，而不是在Dockerfile中完成大量的shell運行步驟（最後只是一個美化的shell腳本）。你失去了一些構建緩存的好處，但是我們已經從使用shell腳本進行配置開始，這是有原因的。