Open russalex83 opened 4 years ago
Having a similar problem. Were you able to sort this out?
I ran into similar issues in Ubuntu 18 with incorrect Node JS versions. I eventually was able to get it all dockerized through trial and error. Try this:
FROM ubuntu:18.04 RUN apt-get update RUN apt-get install -y build-essential openssh-server apache2 RUN apt-get install -y linux-headers-$(uname -r) RUN apt-get install net-tools -y RUN apt-get update RUN apt-get install -y curl git nodejs npm RUN cd /root && git clone https://github.com/sushilks/kumojs.git RUN cd /root/kumojs && npm install && npm run build ADD kumo.cfg /root/kumojs/build/kumo.cfg RUN echo "cd /root/kumojs && npm run server" > /root/run_kumojs.sh RUN chmod +x /root/run_kumojs.sh
You have to get this running elsewhere though -- so that you can run the config wizard/command line and get your config file. Once you have the config file SAVE IT. As long as you don't change your KUMO password it's valid. Even if the devices change IP you can change them manually in the file (but make DHCP reservations so this doesn't happen).
You can also just change the RUN commands at the bottom to /bin/bash and then connect to it, and use the uninitialized node js server's config function to get your kumo config file.
I also have kubernetes manifests, if interested
Thanks for your help. I am not running on Ubuntu, but the similarity is that my install fails during the build phase with a similar message about "tsc: not found". Seems tsc was deprecated. Perhaps my version of Node is too recent and I need to load an older version?
Yeah, you'll need the older version.
BTW That docker file will work on ANY computer with docker installed.
RUN curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash RUN bash -c ". /root/.nvm/nvm.sh && nvm install v6.11.2"
^^ I pulled those from @sushilks's docker file.... looks like you need v6.11.2
Thanks
Sorry to be slow at this, but I have installed node.js version 6.11.2 and have confirmed that this is what is running, but I still get the tcs: command not found error. Any insights? NPM is version 3.10.10 (FYI).
When in doubt: Go to Ubuntu 16. Sorry I'd be in the same boat googling that error as you.
Or you could use docker...
You need to install typescript. Instructions appear to be here: https://dev.to/quentindamianino/how-to-install-typescript-on-ubuntu-33am
On Fedora, the package name is : nodejs-typescript
root@ubuntu18:/home/russ# npm install kumojs
sh: 1: tsc: not found
npm ERR! Linux 5.0.0-23-generic npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build" npm ERR! node v8.10.0 npm ERR! npm v3.5.2 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! kumojs@0.1.3 build:
tsc
npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the kumojs@0.1.3 build script 'tsc'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the kumojs package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! tsc npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs kumojs npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls kumojs npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request: npm ERR! /home/russ/node_modules/kumojs/npm-debug.log npm WARN enoent ENOENT: no such file or directory, open '/home/russ/package.json' npm WARN russ No description npm WARN russ No repository field. npm WARN russ No README data npm WARN russ No license field. npm ERR! Linux 5.0.0-23-generic npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "kumojs" npm ERR! node v8.10.0 npm ERR! npm v3.5.2 npm ERR! code ELIFECYCLE
npm ERR! kumojs@0.1.3 postinstall:
npm run build
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the kumojs@0.1.3 postinstall script 'npm run build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the kumojs package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs kumojs npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls kumojs npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request: npm ERR! /home/russ/npm-debug.log root@ubuntu18:/home/russ#