marlburrow / google-home-notification-gateway Goto Github PK

Sorry, but I'm a newbie to docker....
I've pulled the image successfully...
If I do

docker image ls

I get:

REPOSITORY TAG IMAGE ID CREATED SIZE
marlburrow/ghng latest 6b4c5ad1dd8e 5 weeks ago 440MB

so I tried:

docker run -i --expose=3000 6b4c5ad1dd8e bash

but I get the error:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "bash": executable file not found in $PATH": unknown.

I've tried

docker run -i --expose=3000 6b4c5ad1dd8e start.js

which gives me the error:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "start.js": executable file not found in $PATH": unknown.

Update:

tried:

docker run -p 3000:3000 6b4c5ad1dd8e

and now it seems to run... at least I get something if I go to localhost:3000
TIA

/Søren

Admin password must be entered 2 times during at first use.

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 [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/app/node_modules/.bin:/us$
9 verbose lifecycle [email protected]~start: CWD: /app
10 silly lifecycle [email protected]~start: Args: [ '-c',
10 silly lifecycle   'cross-env NODE_ENV=production NODE_PORT=3000 node start.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] 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 [email protected]
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 [email protected] start: `cross-env NODE_ENV=production NODE_PORT=3000 node start.js`
22 error Exit status 1
23 error Failed at the [email protected] 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.

Raspberry Pi 3 running Raspbian Jessie. Successfully cloned and ran npm install. Then failed with a ton of errors on npm run build.

Here's a gist with the debug log

Quick Googling of npm ERR! code ELIFECYCLE errno 2 did not return any help for me.

Thanks in advance for any help.

First of all, fantastic work ! The project is just what we users wanted for a long time.

However, there's a problem that may annoy a few users like me : the GHome broadcasts even when I'm sleeping, that managed to woke me up several times.

A good idea would be to have a system to enable/disable notifications during certain hours.

Can we get a docker container that builds from this repo for automated deployments?

trace after login/auth on the console :
.......
Executing (default): SELECT identifier, value, createdAt, updatedAt FROM settings AS settings WHERE settings.identifier = 'admin-password';
.....................
but then the the admin GUI stay frozen .. trying to authenticate ........

BR
phil

web interface work but when I use the http get request I receive this error (on two debian linux machine)
Error: get key failed from google
at /home/aldo/google-home-notification-gateway/node_modules/google-tts-api/lib/key.js:27:13
at
at process._tickCallback (internal/process/next_tick.js:182:7)

curl: (52) Empty reply from server

Hi, thank you for this nice project, I hope it hasn't been abandoned.
Recently, Google changed something with their tts service which breaks functionality.
noelportugal/google-home-notifier#46
zlargon/google-tts#17
It should be easily fixed...

Localtunnel isn't stable and the subdomain is random. Serveo works over ssh and can provide predictable subdomains or even custom domains.

Just a suggestion.

Hello
nice job .. i am am trying to use your Gateway.... :-)

you say it easy to send txt2speech to GH through HTTP ( in yourREADME) ...
This is exactly what i am trying to realize ... but there is not lot of documentation
regarding this
i imagine something with curl ....... with JSON data array and the right URL:PORT for the GH

do you have some example ?

BR
phil

Hi,

I am not by any means experienced, but I saw the other person on reddit had this issue and hasn't posted it here yet. I have tried as per your directions "If this step fails with a node-gyp related error, go to node-gyp and follow the instructions for your platform."

[email protected] install C:\GHGateway\google-home-notification-gateway\node_modules\mdns
node-gyp rebuild

I will wait for any other updates or other help. Please remove if I am being a noob. :)