Google Home Notification Gateway (GHNG) is an administrable API allowing your Google devices to receive voice notifications from anything able to send very basics HTTP requests.
The docker container runs perfectly the first time.
However, if I restart the container or stop and start it again, it will never run and ends up giving the following error in the log files.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'start' ]
2 info using npm@5.6.0
3 info using node@v8.11.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle google-home-notification-gateway@1.0.0~prestart: google-home-notification-gateway@1.0.0
6 info lifecycle google-home-notification-gateway@1.0.0~start: google-home-notification-gateway@1.0.0
7 verbose lifecycle google-home-notification-gateway@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle google-home-notification-gateway@1.0.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/app/node_modules/.bin:/us$
9 verbose lifecycle google-home-notification-gateway@1.0.0~start: CWD: /app
10 silly lifecycle google-home-notification-gateway@1.0.0~start: Args: [ '-c',
10 silly lifecycle 'cross-env NODE_ENV=production NODE_PORT=3000 node start.js' ]
11 silly lifecycle google-home-notification-gateway@1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle google-home-notification-gateway@1.0.0~start: Failed to exec start script
13 verbose stack Error: google-home-notification-gateway@1.0.0 start: `cross-env NODE_ENV=production NODE_PORT=3000 node start.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid google-home-notification-gateway@1.0.0
15 verbose cwd /app
16 verbose Linux 4.13.0-41-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
18 verbose node v8.11.1
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error google-home-notification-gateway@1.0.0 start: `cross-env NODE_ENV=production NODE_PORT=3000 node start.js`
22 error Exit status 1
23 error Failed at the google-home-notification-gateway@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
But, if I recreate the container, it will run again, once, before exhibiting the same issue again post restart.
The docker container runs perfectly the first time. However, if I restart the container or stop and start it again, it will never run and ends up giving the following error in the log files.
But, if I recreate the container, it will run again, once, before exhibiting the same issue again post restart.