Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issue with n8n 0.210.0 and above #8

Open
fcecagno opened this issue Jan 13, 2023 · 4 comments
Open

Compatibility issue with n8n 0.210.0 and above #8

fcecagno opened this issue Jan 13, 2023 · 4 comments

Comments

@fcecagno
Copy link

Hi, it looks like the last compatible n8n version is 0.209.4 - later versions have dependency compatibility issues. The installation of the packages results in:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve                                                                                                                                                                                  
npm ERR!                                                                                                                                                                                                             
npm ERR! While resolving: [email protected]                                                                                                                                                                             
npm ERR! Found: [email protected]                                                                                                                                                                                        
npm ERR! node_modules/ioredis
npm ERR!   ioredis@"^5.0.0" from [email protected]
npm ERR!   node_modules/bull
npm ERR!     bull@"^4.10.2" from the root project
npm ERR!   ioredis@"^5.2.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional ioredis@"^4.28.3" from [email protected]
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.2.45" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/ioredis
npm ERR!   peerOptional ioredis@"^4.28.3" from [email protected]
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.2.45" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

This is the Dockerfile we're using to build a puppeteer enabled image for n8n. Build it with docker build -t n8n-local .:

FROM n8nio/n8n:0.210.2

# Installs latest Chromium package
RUN apk add --no-cache \
  chromium \
  nss \
  freetype \
  harfbuzz \
  ttf-freefont \
  yarn

# Tell Puppeteer to skip installing Chrome. We'll be using the installed package.
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true \
  PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium-browser

# Install n8n-nodes-puppeteer
RUN cd /usr/local/lib/node_modules/n8n \
 && npm install n8n-nodes-puppeteer

# Install fonts
RUN apk --no-cache add --virtual fonts msttcorefonts-installer fontconfig \
 && update-ms-fonts \
 && fc-cache -f \
 && apk del fonts \
 && find  /usr/share/fonts/truetype/msttcorefonts/ -type l -exec unlink {} \; \
 && rm -rf /root /tmp/* /var/cache/apk/* && mkdir /root
@therysin
Copy link

Same issue here.

@Loocos
Copy link

Loocos commented Mar 23, 2023

I made it works on a debian python based dockerfile (https://github.com/naskio/n8n-nodes-python).

I was able to use the node but I got this error :
Failed to launch the browser process! [No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

There's 3 ways of fixing this :

Are you still having issue to build the docker image ? I can share mine if needed

@fugohan
Copy link

fugohan commented Aug 20, 2023

I think its not working on 1.1+

@keajer
Copy link

keajer commented May 7, 2024

@Loocos Mind sharing your docker file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants