Permission Error in Portainer When Creating Images for Installing Community Nodes

[Lucas_Haas]

Describe the problem/error/question

I’m trying to install a community node, and I’m on Version 1.36.4 self-hosted. When I try to access community nodes, it says I need to install manually. Since I’m using Portainer, I tried to create an image, but I’m getting a permission error. Below is how I’m attempting to execute the image.

What is the error message (if any)?

This is the error I get when trying to build the image.

Can someone help me with this?

Share the output returned by the last node

Information on your n8n setup

• Version 1.36.4
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): queue mode
• Running n8n via (Docker, npm, n8n cloud, desktop app): Portainer
• Ubuntu 20.04

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[barn4k]

hello @Lucas_Haas

Have you tried to execute that command under the root or with sudo privileges?
The user, under which the npm is being executed, does not have enough permissions to create folders.

[BramKn]

Welcome to the community @Lucas_Haas

Never knew you could do this in portainer thanks!

Also nice to see people using my node(s)

This is a topic to help you out, not sure if it is up to date but should be good.

How to build own image with custom node modules?

Hey everyone! hint, how to correctly prepare dockerfile for custom modules version 1 ? my Dockerfile: FROM n8nio/n8n USER root RUN apk --no-cache add python3 ffmpeg imagemagick-dev imagemagick py3-pip RUN npm install -g bcrypt body-parser fcm-push #RUN mkdir -p /root/.n8n/nodes && cd /root/.n8n/nodes && npm link bcrypt body-parser fcm-push The line with one of the attempts to place the link in ~/.n8n/nodes is commented out, but at the time of building the image there is no .n8n folder in it…

[Lucas_Haas]

Hello guys, I managed to deploy with this command:

FROM n8nio/n8n:latest

USER root

RUN mkdir /home/node/.n8n/nodes

WORKDIR /home/node/.N8N/nodes

RUN npm i n8n-nodes-pdfkit

However, after updating n8n, the node still does not appear for me to use…

[Lucas_Haas]

I followed the steps in this video: LINK. It instructs to change the version name in the n8n stack to the name I gave the image. However, when I make this change and update it, my old workflows throw errors, and I can no longer use n8n.