Now its complaining that it can’t access the /usr/local/lib/node_modules/ directory.
Now I’ve addes the USER root and change back to USER node to see if that helps.
It does insall the pythong make an npm etc etc.
But when it goes to the /user/local/node_modules directory it quits
[n8n 3/3] RUN cd /usr/local/lib/node_modules/n8n && npm install n8n-nodes-telepilot:
37.49 npm ERR! code 1
37.49 npm ERR! path /usr/local/lib/node_modules/n8n/node_modules/tdl
37.49 npm ERR! command failed
37.49 npm ERR! command sh -c node-gyp-build
37.49 npm ERR! make: Entering directory ‘/usr/local/lib/node_modules/n8n/node_modules/tdl/build’
37.49 npm ERR! CC(target) Release/obj.target/nothing/node_modules/node-addon-api/nothing.o
37.49 npm ERR! make: Leaving directory ‘/usr/local/lib/node_modules/n8n/node_modules/tdl/build’
37.49 npm ERR! make: cc: No such file or directory
Now should I manually create the whole structure … or or …
You have some advice on this area ?
Thanks !
FROM n8nio/n8n:latest
USER root
RUN apk add --update python3 py3-pip make npm
RUN cd /usr/local/lib/node_modules/n8n && npm install n8n-nodes-telepilot
USER node
ENTRYPOINT [“docker-entrypoint.sh”]
Why do you try to install python, pip and npm ? Yo juste need to install your missing package and it should work.
Npm is already install on docker images
It was complaining that it couldn’t find make ( showed in the output ).
The python, npm etc is there now because of trial and error. I will remove it from the Dockerfile.
The path you are using is not correct it should be…
RUN cd /home/node/.n8n/custom && npm install n8n-nodes-telepilot
But if you are installing a community node you can just do it from the n8n interface under the settings which is a lot easier, You can find that option here: GUI installation | n8n Docs
I did try to add it through the community browser, but it failed.
On gitbhub of Telepilot it said that if using the Docker route, it should be added during
the Docker n8n installation.
I have just given it a go and it fails to install from the UI for me as well, I guess the docker approach is the best option which is annoying.
Looking at the package on npm I forgot that this is one that includes some precompiled binaries so it would need the dockerfile route using the correct path.