Docker error after upgrading to 0.166 or above

[mryoaz]

Describe the bug
When I upgrade the image of n8n to 0.166.0 or above. I get this docker error:
n8n | # n8n | # Fatal error in , line 0 n8n | # unreachable code n8n | # n8n | # n8n | # n8n | #FailureMessage Object: 0x7e8684cc n8n exited with code 133

Environment:

• Docker version: 20.10.14, build a224086
• docker-compose version: 1.21.0, build unknown
• OS: Raspbian Linux 10
• Kernel and CPU: Linux 5.10.103-v7+ on armv7l
• n8n Version: 0.166.00

Additional context
I use docker-compose. The n8n part of the file (traefik works fine):

n8n: image: n8nio/n8n:0.166.0 restart: always container_name: n8n ports: - "5678:5678" labels: - traefik.enable=true - traefik.http.routers.n8n.rule=Host(n8n.****.nl) - traefik.http.routers.n8n.tls=true - traefik.http.routers.n8n.entrypoints=web,websecure - traefik.http.routers.n8n.tls.certresolver=mytlschallenge - traefik.http.routers.n8n.service=n8n - traefik.http.services.n8n.loadbalancer.server.port=5678 - traefik.http.middlewares.n8n.headers.SSLRedirect=true - traefik.http.middlewares.n8n.headers.STSSeconds=315360000 - traefik.http.middlewares.n8n.headers.browserXSSFilter=true - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true - traefik.http.middlewares.n8n.headers.forceSTSHeader=true - traefik.http.middlewares.n8n.headers.SSLHost=****.nl - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true - traefik.http.middlewares.n8n.headers.STSPreload=true environment: - N8N_BASIC_AUTH_ACTIVE=true - N8N_BASIC_AUTH_USER=**** - N8N_BASIC_AUTH_PASSWORD=**** - N8N_HOST=n8n.****.nl - N8N_PORT=5678 - N8N_PROTOCOL=https - NODE_ENV=production - WEBHOOK_TUNNEL_URL=https://n8n.****.nl/ - GENERIC_TIMEZONE=Europe/Amsterdam - N8N_USER_MANAGEMENT_DISABLED=true volumes: - /home/pi/.n8n:/home/node/.n8n network_mode: host

[janober]

Are you the same person who posted this in the forum?
https://community.n8n.io/t/docker-compose-up-fail-for-unexpected-reson-after-upgrading-from-0-159-1-to-0-169-0/12560

[janober]

Generally assume it has to do with the build for linux/arm/v7 which probably got introduced with the switch to Node.js v16. Sadly have honestly no experience with it and do not have one myself.

[mryoaz]

Are you the same person who posted this in the forum? https://community.n8n.io/t/docker-compose-up-fail-for-unexpected-reson-after-upgrading-from-0-159-1-to-0-169-0/12560

No. That's not me.
Thanks. I will also participate in that discussion.

[florian-guillemard]

Hi,
It appears that the error came from the alpine image 3.15..
Maybe changing back the node:16-alpine into node:14.15-alpine will work ?!

[florian-guillemard]

I just tried changing at that line and it works

n8n/docker/images/n8n/Dockerfile

Line 1 in 016aeaa

FROM node:16-alpine

[janober]

Ah yes, that will work for sure, but is not really solving the problem as we are then using again Node.js v14 which we do not want. We want to use Node.js v16 that is why that change got made.

So the question is what does need to change except that one line.

[CCninja86]

There is a fix for this. You just need to upgrade your version of docker and libseccomp. Details are here: https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#musl_1.2

Docker 19.03.9 (which contains backported moby commit 89fabf0) or greater, AND libseccomp 2.4.2 or greater

[mryoaz]

Thank you @CCninja86
I found an article which helped me: https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/

I got it working by updating libseccomp2 (version 2.5.1-1~bpo10+1).
Docker was already up to date: 20.10.14.

[florian-guillemard]

Thanks a lot @mryoaz !