Twitch-watcher
Twitch-watcher copied to clipboard
D3vl0per
Raspberry pi
Will this work with the raspberry pi because I've been trying it on it and I keep getting errors.
It might be something simple im a little new to linux.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'start',
1 verbose cli 'docker-compose.yml',
1 verbose cli '-d' ]
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:/home/pi/.local/share/Trash/files/Valorant-watcher-master/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle [email protected]~start: CWD: /home/pi/.local/share/Trash/files/Valorant-watcher-master
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node app "docker-compose.yml"' ]
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: node app "docker-compose.yml"
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.node app "docker-compose.yml"
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 ]
13 verbose stack Error: [email protected] start: node app "docker-compose.yml"
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "start" "docker-compose.yml" "-d"
22 error [email protected] start: node app "docker-compose.yml"
What are you typed in the console? @Kronull
- node app
- npm start
- docker-compose up
- docker-compose up -d
- Else:
Come for here: https://gitter.im/valorant-watcher/support I want to talk this with you.
He use this command: npm start docker-compose up -d
npm start
OR
docker-compose up -d
Do not mix it!
I think that valorant-watcher do not work on rpi because image https://hub.docker.com/r/d3vm/valorant-watcher/tags is based on amd64 architecture. To make it work on rpi you would have to create additional image with arm64 arch.
@D3vl0per You might add something like that to the Dockerfile and it might work:
FROM arm64v8/node:13.12.0-alpine3.10 AS arm64v8
LABEL maintainer="D3v <[email protected]>"
RUN apk add --no-cache chromium nss freetype freetype-dev harfbuzz ca-certificates ttf-freefont
WORKDIR /usr/src/app
COPY . .
RUN npm install
CMD ["npm","start"]
when running on rpi i get this error
🔎 Checking config file...
✅ Json config found!
(node:6658) UnhandledPromiseRejectionWarning: ReferenceError: e is not defined
at readLoginData (/home/pi/Valorant-watcher/app.js:201:31)
at main (/home/pi/Valorant-watcher/app.js:355:18)
at Object.
For me it's working perfectly fine on a RPi 4B (armv7l), which version of NodeJS do you use?
@yohudood Nice catch! https://github.com/D3vl0per/Valorant-watcher/blob/fa07ae02575ed22e83b5ca61a00d4c3de0810ddb/app.js#L200-L201
now a new error
🔎 Checking config file... ✅ Json config found!
📱 Launching browser... (node:4480) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! spawn /usr/bin/chromium ENOENT
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md
at onClose (/home/pi/Valorant-watcher/node_modules/puppeteer-core/lib/Launcher.js:750:14)
at ChildProcess.helper.addEventListener.error (/home/pi/Valorant-watcher/node_modules/puppeteer-core/lib/Launcher.js:741:65)
at ChildProcess.emit (events.js:198:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:4480) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:4480) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
sorry it was my own fault i configured chromium instead of chromium-browser