docker-node-mongo | /bin/sh: 1: [npm: not found

[daftpy]

Attempting to run docker-compose up seems to lead to an error showing that npm is not found.

Not too sure where to move forward from here. I am using Windows 10.

docker-node-mongo | /bin/sh: 1: [npm: not found
mongo    | 2020-03-07T07:23:53.211+0000 I  CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=585a4058e921
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] db version v4.2.3
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] git version: 6874650b362138df74be53d366bbefc321ea32d4
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] allocator: tcmalloc
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] modules: none
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten] build environment:
mongo    | 2020-03-07T07:23:53.215+0000 I  CONTROL  [initandlisten]     distmod: ubuntu1804
mongo    | 2020-03-07T07:23:53.216+0000 I  CONTROL  [initandlisten]     distarch: x86_64
mongo    | 2020-03-07T07:23:53.216+0000 I  CONTROL  [initandlisten]     target_arch: x86_64
mongo    | 2020-03-07T07:23:53.216+0000 I  CONTROL  [initandlisten] options: { net: { bindIp: "*" } }
mongo    | 2020-03-07T07:23:53.216+0000 I  STORAGE  [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
mongo    | 2020-03-07T07:23:53.216+0000 I  STORAGE  [initandlisten]
mongo    | 2020-03-07T07:23:53.216+0000 I  STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongo    | 2020-03-07T07:23:53.216+0000 I  STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongo    | 2020-03-07T07:23:53.216+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],
mongo    | 2020-03-07T07:23:53.782+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565833:782705][1:0x7f8b5e8e0b00], txn-recover: Recovering log 18 through 19
mongo    | 2020-03-07T07:23:53.814+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565833:814579][1:0x7f8b5e8e0b00], txn-recover: Recovering log 19 through 19
docker-node-mongo exited with code 127
mongo    | 2020-03-07T07:23:53.878+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565833:878139][1:0x7f8b5e8e0b00], txn-recover: Main recovery loop: starting at 18/4736 to 19/256
mongo    | 2020-03-07T07:23:53.934+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565833:934777][1:0x7f8b5e8e0b00], txn-recover: Recovering log 18 through 19
mongo    | 2020-03-07T07:23:53.983+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565833:983694][1:0x7f8b5e8e0b00], txn-recover: Recovering log 19 through 19
mongo    | 2020-03-07T07:23:54.018+0000 I  STORAGE  [initandlisten] WiredTiger message [1583565834:18817][1:0x7f8b5e8e0b00], txn-recover: Set global recovery timestamp: (0, 0)
mongo    | 2020-03-07T07:23:54.053+0000 I  RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
mongo    | 2020-03-07T07:23:54.058+0000 I  STORAGE  [initandlisten] Timestamp monitor starting
mongo    | 2020-03-07T07:23:54.059+0000 I  CONTROL  [initandlisten]
mongo    | 2020-03-07T07:23:54.059+0000 I  CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongo    | 2020-03-07T07:23:54.059+0000 I  CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongo    | 2020-03-07T07:23:54.059+0000 I  CONTROL  [initandlisten]
mongo    | 2020-03-07T07:23:54.062+0000 I  SHARDING [initandlisten] Marking collection local.system.replset as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.063+0000 I  STORAGE  [initandlisten] Flow Control is enabled on this deployment.
mongo    | 2020-03-07T07:23:54.063+0000 I  SHARDING [initandlisten] Marking collection admin.system.roles as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.063+0000 I  SHARDING [initandlisten] Marking collection admin.system.version as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.064+0000 I  SHARDING [initandlisten] Marking collection local.startup_log as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.065+0000 I  FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
mongo    | 2020-03-07T07:23:54.067+0000 I  SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.068+0000 I  NETWORK  [listener] Listening on /tmp/mongodb-27017.sock
mongo    | 2020-03-07T07:23:54.068+0000 I  SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version: <unsharded>
mongo    | 2020-03-07T07:23:54.068+0000 I  NETWORK  [listener] Listening on 0.0.0.0
mongo    | 2020-03-07T07:23:54.068+0000 I  NETWORK  [listener] waiting for connections on port 27017
docker-node-mongo exited with code 127

[IamLizu]

For me, it turns out that I was doing CMD ["npm", 'start']. And double quoting start solved it.

[calliduscete]

For me, it turns out that I was doing CMD ["npm", 'start']. And double quoting start solved it.

saved my life lol