Fatal编程技术网
  • mongodb/
  • Mongodb Mongo docker容器在切分时停止，容器未成功创建

Mongodb Mongo docker容器在切分时停止，容器未成功创建

mongodb docker docker-compose

Mongodb Mongo docker容器在切分时停止，容器未成功创建,mongodb,docker,docker-compose,Mongodb,Docker,Docker Compose,我正在尝试使用docker compose启动mongo docker容器，它在我的前两次尝试中都有效，现在我无法再让它工作，无论何时我尝试运行： docker-compose up 执行将在此行停止： mondodb_container_1 | 2020-03-07T04:42:00.000+0000 I SHARDING [ftdc] Marking collection local.oplog.rs as collection version: <unsharded>

我正在尝试使用docker compose启动mongo docker容器，它在我的前两次尝试中都有效，现在我无法再让它工作，无论何时我尝试运行：

docker-compose up
执行将在此行停止：

mondodb_container_1  | 2020-03-07T04:42:00.000+0000 I  SHARDING [ftdc] Marking collection local.oplog.rs as collection version: <unsharded>
以下是整个执行过程：

Recreating microservices-test_mondodb_container_1 ... done                                                                                                         Attaching to microservices-test_mondodb_container_1
mondodb_container_1  | 2020-03-07T04:47:33.498+0000 I  CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
mondodb_container_1  | 2020-03-07T04:47:33.504+0000 I  CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=017a4a41dad8
mondodb_container_1  | 2020-03-07T04:47:33.504+0000 I  CONTROL  [initandlisten] db version v4.2.3
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] git version: 6874650b362138df74be53d366bbefc321ea32d4
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] allocator: tcmalloc
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] modules: none
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] build environment:
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten]     distmod: ubuntu1804
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten]     distarch: x86_64
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten]     target_arch: x86_64
mondodb_container_1  | 2020-03-07T04:47:33.505+0000 I  CONTROL  [initandlisten] options: { net: { bindIp: "*" } }
mondodb_container_1  | 2020-03-07T04:47:33.506+0000 I  STORAGE  [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
mondodb_container_1  | 2020-03-07T04:47:33.506+0000 I  STORAGE  [initandlisten]
mondodb_container_1  | 2020-03-07T04:47:33.506+0000 I  STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mondodb_container_1  | 2020-03-07T04:47:33.506+0000 I  STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mondodb_container_1  | 2020-03-07T04:47:33.506+0000 I  STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=482M,cache_overflow=(file_max=0M),session_max=33000,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,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress],
mondodb_container_1  | 2020-03-07T04:47:34.389+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:389436][1:0x7fb169ed1b00], txn-recover: Recovering log 18 through 19
mondodb_container_1  | 2020-03-07T04:47:34.454+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:454638][1:0x7fb169ed1b00], txn-recover: Recovering log 19 through 19
mondodb_container_1  | 2020-03-07T04:47:34.556+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:556820][1:0x7fb169ed1b00], txn-recover: Main recovery loop: starting at 18/6272 to 19/256
mondodb_container_1  | 2020-03-07T04:47:34.687+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:687007][1:0x7fb169ed1b00], txn-recover: Recovering log 18 through 19
mondodb_container_1  | 2020-03-07T04:47:34.795+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:795297][1:0x7fb169ed1b00], txn-recover: Recovering log 19 through 19
mondodb_container_1  | 2020-03-07T04:47:34.861+0000 I  STORAGE  [initandlisten] WiredTiger message [1583556454:861429][1:0x7fb169ed1b00], txn-recover: Set global recovery timestamp: (0, 0)
mondodb_container_1  | 2020-03-07T04:47:34.914+0000 I  RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
mondodb_container_1  | 2020-03-07T04:47:34.920+0000 I  STORAGE  [initandlisten] Timestamp monitor starting
mondodb_container_1  | 2020-03-07T04:47:34.925+0000 I  CONTROL  [initandlisten]
mondodb_container_1  | 2020-03-07T04:47:34.926+0000 I  CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mondodb_container_1  | 2020-03-07T04:47:34.926+0000 I  CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mondodb_container_1  | 2020-03-07T04:47:34.926+0000 I  CONTROL  [initandlisten]
mondodb_container_1  | 2020-03-07T04:47:34.929+0000 I  SHARDING [initandlisten] Marking collection local.system.replset as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:34.932+0000 I  STORAGE  [initandlisten] Flow Control is enabled on this deployment.
mondodb_container_1  | 2020-03-07T04:47:34.932+0000 I  SHARDING [initandlisten] Marking collection admin.system.roles as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:34.932+0000 I  SHARDING [initandlisten] Marking collection admin.system.version as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:34.935+0000 I  SHARDING [initandlisten] Marking collection local.startup_log as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:34.935+0000 I  FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
mondodb_container_1  | 2020-03-07T04:47:34.937+0000 I  SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:34.937+0000 I  NETWORK  [listener] Listening on /tmp/mongodb-27017.sock
mondodb_container_1  | 2020-03-07T04:47:34.937+0000 I  NETWORK  [listener] Listening on 0.0.0.0
mondodb_container_1  | 2020-03-07T04:47:34.937+0000 I  NETWORK  [listener] waiting for connections on port 27017
mondodb_container_1  | 2020-03-07T04:47:34.938+0000 I  SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version: <unsharded>
mondodb_container_1  | 2020-03-07T04:47:35.000+0000 I  SHARDING [ftdc] Marking collection local.oplog.rs as collection version: <unsharded>
我试过：

    ->Mongo container v4.2
    ->Mongo container v4.0
    ->Restarting Docker 
    ->Change the TCP port
我在MongoDB网站上看到了关于这一点的公开声明，但是他们说这在mongo的v4上得到了解决

有人知道我怎样才能克服这个问题吗？

我也遇到了这个问题，这让我发疯了

好消息是它确实在工作。您看到的输出只是日志，这是最后一条日志消息。如果您打开一个新终端并执行以下操作：

docker ps -a
然后您应该看到该容器正在运行。然后，您可以执行以下操作：

docker exec -it [the container name] bash
您将在容器中，可以运行
mongo-uroot-p
来实际连接到mongo

docker ps -a

docker exec -it [the container name] bash