NPM not found? about homebridge-docker HOT 9 OPEN

probably your docker containers don't have network and therefore the apt-get failed. I had this problem on a raspberrypi.

from homebridge-docker.

no reason it shouldn't have network... it's in docker build, after all. I have a few other containers up and running doing things with the network

from homebridge-docker.

try to delete the cache and see if the apt-get steps runs alright...

from homebridge-docker.

@snizzleorg there is no cache, it's using docker image (which has no cache initially)

from homebridge-docker.

it looks like the Dockerfile.specific is never getting into the Dockerfile...

something to do with this perhaps:

sed: -e expression #1, char 1: unknown command: `.'

from homebridge-docker.

@snizzleorg In the homebridge.sh file there's an offending '.bak' in the SED expression... I don't think it should be there, and seems to be causing the problem.

from homebridge-docker.

yeah but the docker image is built by the script and the interims images are stored on your computer. so the the one you built doesn't have nam installed (probably because during the build there was no network)

from homebridge-docker.

@oehokie Just saw your last comments. It did work for me... but maybe it's been changed since I used it to build the image.

from homebridge-docker.

The problem is that the base image doesn't seem to actually ship with node? This is using a vanilla Jessy image as the upstream. NPM is straight up not installed at any time during build. What OS are you running this on? I'm seeing this on Ubuntu 16.04

from homebridge-docker.