Giter Site home page Giter Site logo

docker-node-mongo's Introduction

Docker Node MongoDB Example

Simple example of a dockerized Node/Mongo app

Image

Quick Start

# Run in Docker
docker-compose up
# use -d flag to run in background

# Tear down
docker-compose down

# To be able to edit files, add volume to compose file
volumes: ['./:/usr/src/app']

# To re-build
docker-compose build

docker-node-mongo's People

Contributors

bradtraversy avatar bruno-silva5 avatar dependabot[bot] avatar lifeeric avatar victorlandim avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-node-mongo's Issues

Cant connect to existing mongo container

here is my docker-compose.yml:

version: '3'
services:
  app:
    container_name: docker-node-mongo
    restart: always
    build: .
    ports:
      - '3001:3000'
#    external_links:
#      - mongo
#  mongo:
#    container_name: mongo
#    image: mongo
#    ports:
#      - '27017:27017'

my index.js

mongoose
  .connect(
    'mongodb://127.0.0.1:27017/test2',
    { useNewUrlParser: true }
  )
  .then(() => console.log('MongoDB Connected'))
  .catch(err => console.log("errorErrorError"));

and this when i run docker container ls -a

6f14a98e2d51        dockernodemongo_app       "npm start"              7 minutes ago       Up 7 minutes            0.0.0.0:3001->3000/tcp                     docker-node-mongo

f3fb55dad886        mongo                     "docker-entrypoint.sā€¦"   19 minutes ago      Up 19 minutes           127.0.0.1:27017->27017/tcp                 mongo

this is the error when i type docker logs docker-node-mongo

Server running...
{ MongoNetworkError: failed to connect to server [mongo:27017] on first connect [MongoNetworkError: getaddrinfo EAI_AGAIN mongo mongo:27017]
    at Pool.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/topologies/server.js:562:11)
    at Pool.emit (events.js:182:13)
    at Connection.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:316:12)
    at Object.onceWrapper (events.js:273:13)
    at Connection.emit (events.js:182:13)
    at Socket.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:245:50)
    at Object.onceWrapper (events.js:273:13)
    at Socket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  name: 'MongoNetworkError',
  message:
   'failed to connect to server [mongo:27017] on first connect [MongoNetworkError: getaddrinfo EAI_AGAIN mongo mongo:27017]',
  errorLabels: [ 'TransientTransactionError' ],
  [Symbol(mongoErrorContextSymbol)]: {} }

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

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

Cannot start service mongo

ERROR: for mongo Cannot start service mongo: driver failed programming external connectivity on endpoint mongo (90b8dd1b53fe2ff77d1468cff3a1f5f73e7c202fb66fb0678278aeab50278df1): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:27017:tcp:172.20.0.2:27017: input/output error
ERROR: Encountered errors while bringing up the project.

docker-compose.yml:
version: '3'
services:
app:
container_name: docker-node-mongo
restart: always
build: .
ports:
- '80:3000'
links:
- mongo
mongo:
container_name: mongo
image: mongo
ports:
- '27017:27017'

package.json:
{
"name": "docker-node-mongo",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "node index.js"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"body-parser": "^1.18.3",
"ejs": "^2.6.1",
"express": "^4.16.3",
"mongoose": "^5.2.7"
}
}

Readme ommision

You missed out the first step, which shld be docker-compose build although you mentioned it at the last point for rebuild. Without building the image first the docker-compose up will fail.

npm ERR! errno ENOTFOUND

After typing this below command
sudo docker-compose up

Show Error On npm installation

npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/array-flatten/-/array-flatten-1.1.1.tgz failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-11-13T18_22_45_132Z-debug.log

I can't find any solution

MongoNetworkError: failed to connect to server

Hello everyone!

I dont have any changes after the clone.
After running the command: docker-compose up.
i got this output:

docker-node-mongo | Server running...
docker-node-mongo | { MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
docker-node-mongo |     at Pool.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/topologies/server.js:562:11)
docker-node-mongo |     at Pool.emit (events.js:198:13)
docker-node-mongo |     at Connection.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:316:12)
docker-node-mongo |     at Object.onceWrapper (events.js:286:20)
docker-node-mongo |     at Connection.emit (events.js:198:13)
docker-node-mongo |     at Socket.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:245:50)
docker-node-mongo |     at Object.onceWrapper (events.js:286:20)
docker-node-mongo |     at Socket.emit (events.js:198:13)
docker-node-mongo |     at emitErrorNT (internal/streams/destroy.js:91:8)
docker-node-mongo |     at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
docker-node-mongo |     at process._tickCallback (internal/process/next_tick.js:63:19)
docker-node-mongo |   name: 'MongoNetworkError',
docker-node-mongo |   message:
docker-node-mongo |    'failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]',
docker-node-mongo |   errorLabels: [ 'TransientTransactionError' ],
docker-node-mongo |   [Symbol(mongoErrorContextSymbol)]: {} }

can someone help?
Thank you :-)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    šŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. šŸ“ŠšŸ“ˆšŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ā¤ļø Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.