Just did a quick test of this branch. I did nothing more than checking it out, make and then docker-compose up, so I might have missed a step, maybe around credentials? Also, why is it trying to connect to the EC2 metadata endpoint at 169.254.169.254?
$ docker-compose up
Starting s3photoapp_photo-storage_1 ... done
Starting s3photoapp_photo-filter_1 ... done
Starting s3photoapp_web-client_1 ... done
Attaching to s3photoapp_photo-filter_1, s3photoapp_photo-storage_1, s3photoapp_web-client_1
photo-storage_1 |
photo-storage_1 | > photo-storage@1.0.0 prod /app
photo-storage_1 | > node server.js
photo-storage_1 |
photo-filter_1 |
photo-filter_1 | > photo-filter@1.0.0 prod /app
photo-filter_1 | > node server.js
photo-filter_1 |
photo-filter_1 | Photo Filter API listening on http://localhost:3002
photo-storage_1 | Photo Storage API listening on http://localhost:3001
web-client_1 |
web-client_1 | > web-client@0.0.0 prod /app
web-client_1 | > node ./bin/www
web-client_1 |
web-client_1 | Listening on port 3000
web-client_1 | ERROR: Unable to create or describe required table in DynamoDB { Error: connect ECONNREFUSED 169.254.169.254:80
web-client_1 | at Object.exports._errnoException (util.js:1020:11)
web-client_1 | at exports._exceptionWithHostPort (util.js:1043:20)
web-client_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)
web-client_1 | message: 'Missing credentials in config',
web-client_1 | code: 'CredentialsError',
web-client_1 | errno: 'ECONNREFUSED',
web-client_1 | syscall: 'connect',
web-client_1 | address: '169.254.169.254',
web-client_1 | port: 80,
web-client_1 | time: 2018-08-17T13:21:27.232Z,
web-client_1 | originalError:
web-client_1 | { message: 'Could not load credentials from any providers',
web-client_1 | code: 'CredentialsError',
web-client_1 | errno: 'ECONNREFUSED',
web-client_1 | syscall: 'connect',
web-client_1 | address: '169.254.169.254',
web-client_1 | port: 80,
web-client_1 | time: 2018-08-17T13:21:27.231Z,
web-client_1 | originalError:
web-client_1 | { code: 'ECONNREFUSED',
web-client_1 | errno: 'ECONNREFUSED',
web-client_1 | syscall: 'connect',
web-client_1 | address: '169.254.169.254',
web-client_1 | port: 80,
web-client_1 | message: 'connect ECONNREFUSED 169.254.169.254:80' } } }
web-client_1 |
web-client_1 | npm ERR! Linux 4.9.93-linuxkit-aufs
web-client_1 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "prod"
web-client_1 | npm ERR! node v6.14.4
web-client_1 | npm ERR! npm v3.10.10
web-client_1 | npm ERR! code ELIFECYCLE
web-client_1 | npm ERR! web-client@0.0.0 prod: `node ./bin/www`
web-client_1 | npm ERR! Exit status 1
web-client_1 | npm ERR!
web-client_1 | npm ERR! Failed at the web-client@0.0.0 prod script 'node ./bin/www'.
web-client_1 | npm ERR! Make sure you have the latest version of node.js and npm installed.
web-client_1 | npm ERR! If you do, this is most likely a problem with the web-client package,
web-client_1 | npm ERR! not with npm itself.
web-client_1 | npm ERR! Tell the author that this fails on your system:
web-client_1 | npm ERR! node ./bin/www
web-client_1 | npm ERR! You can get information on how to open an issue for this project with:
web-client_1 | npm ERR! npm bugs web-client
web-client_1 | npm ERR! Or if that isn't available, you can get their info via:
web-client_1 | npm ERR! npm owner ls web-client
web-client_1 | npm ERR! There is likely additional logging output above.
web-client_1 |
web-client_1 | npm ERR! Please include the following file with any support request:
web-client_1 | npm ERR! /app/npm-debug.log
s3photoapp_web-client_1 exited with code 1
Hi Jon,
Just did a quick test of this branch. I did nothing more than checking it out,
makeand thendocker-compose up, so I might have missed a step, maybe around credentials? Also, why is it trying to connect to the EC2 metadata endpoint at 169.254.169.254?