Commit History
-
Update Dockerfile
Verified signature6901091
-
Update Dockerfile
Verified signature21625ec
-
Update Dockerfile
Verified signaturebba45a9
-
Update Dockerfile
Verified signature42a6c33 -
Update Dockerfile
Verified signaturef13b0ce -
Update Dockerfile
Verified signature03753b1 -
Update entrypoint.sh
Verified signaturefed70ce -
Update Dockerfile
Verified signature4c91ddb -
Update Dockerfile
Verified signature65cfd8f -
Update entrypoint.sh
Verified signature2ae7c17 -
Update Dockerfile
Verified signature9640baa -
Update entrypoint.sh
Verified signature60f8ab3 -
Update Dockerfile
Verified signature6732fd5 -
Update Dockerfile
Verified signature8ac43e4 -
Update Dockerfile
Verified signatureaffa593
-
Update Dockerfile
Verified signature8eff895
-
Update Dockerfile
Verified signature9cf3209
-
Update Dockerfile
Verified signatureb38b25a
-
Update Dockerfile
Verified signature4868048 -
Create entrypoint.sh
Verified signature364b303
-
Update Dockerfile
Verified signaturef6a3bd2
-
Update Dockerfile
Verified signaturebe8c58d -
Update Dockerfile
Verified signature394a1d7 -
Update Dockerfile
Verified signatureFROM node:20-alpine USER root # 1) Easy upgrades: change only this line later # Current stable is 2.4.6 (pin for reproducible builds) ARG N8N_VERSION=2.4.6 # 2) System deps (keep chromium + build tools) RUN apk add --no-cache \ git \ python3 \ make \ g++ \ build-base \ cairo-dev \ pango-dev \ chromium \ postgresql-client \ tzdata # 3) Puppeteer/Chromium config ENV PUPPETEER_SKIP_DOWNLOAD=true # If chromium-browser doesn't work in your Space logs, switch to /usr/bin/chromium ENV PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium-browser # 4) n8n config # Store user data in /data (HF persistent storage usually mounts here if enabled) ENV N8N_USER_FOLDER=/data/.n8n # Listen on all interfaces inside the container ENV N8N_LISTEN_ADDRESS=0.0.0.0 # (Optional) Keep this true to avoid permission warnings ENV N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true # 5) If you REALLY need Code node unrestricted imports (security risk): # Prefer setting these in HF "Secre…efb781d -
Update Dockerfile
Verified signature6258042
-
Update Dockerfile
Verified signature3d21446 -
Update Dockerfile
Verified signature6f02767
-
Delete 2kwievovbkvzkl5skdnop7jy1v6x0f.html
Verified signature9e77360 -
Create 2kwievovbkvzkl5skdnop7jy1v6x0f.html (#10)
Verified signature- Create 2kwievovbkvzkl5skdnop7jy1v6x0f.html (b72b19ef63bb94a92163cc2acff0e7cae79b7cb8)4463f84
-
Update Dockerfile (#9)
Verified signature- Update Dockerfile (a7ecbc5874e150ebf28fafdab0fc141b3d7f8b98) Co-authored-by: ffff <jolbbb@users.noreply.huggingface.co>e52da94
-
Update README.md
Verified signature08109f7 -
Update README.md
Verified signature3f863c9 -
Update README.md
Verified signature53ca0c7 -
Update README.md
Verified signatured96c7d8 -
Upgrade to @1.116.2 (#7)
Verified signature- Upgrade to @1.116.2 (2b2fd5cb19524523428e4113a0604494876df764)e59aebe
-
Update Dockerfile
Verified signaturec310f3c -
Upgrade to 1.115.3 (#6)
Verified signature- Upgrade to 1.115.3 (8347abc74aff5ddedb56a786650fb48f02cb21a0)76a78ad
-
Update Dockerfile
Verified signature5776034 -
Update Dockerfile
Verified signature7841d9b -
Update Dockerfile
Verified signatured2b4c55 -
Forcez un nouveau commit SHA (#5)
Verified signature- Forcez un nouveau commit SHA (b86f879245111b4ae5d571b5e209b3dca3b88b3a)af24f65 -
Update Dockerfile
Verified signaturefc01053 -
Update Dockerfile
Verified signaturef19fdbb -
Update Dockerfile
Verified signatured9e4111 -
fix(docker): Resolve EISDIR error on n8n startup
Verified signaturefix(docker): Resolve EISDIR error on n8n startup Corrects a runtime error "EISDIR: illegal operation on a directory" that occurs with n8n version 1.115.2 and later. The issue was caused by the Dockerfile pre-creating a `/root/.n8n/config` directory, which conflicts with n8n's expectation of a configuration file at that location. This fix modifies the RUN command to only create the base `/root/.n8n` directory, allowing n8n to initialize its own internal file and folder structure correctly on first boot. ------ ## fix(docker): Resolve `EISDIR` Error During Application Startup ### Problem When building and running a Docker container with n8n version `@1.115.2`, the application fails to start, throwing the following runtime error: -------- This error indicates that a file operation (`readFileSync`) was attempted on a path that is a directory, not a file. The root cause was traced to the `Dockerfile`, which explicitly created several subdirectories, including one at the `CONFIG_PATH` (`/r…c91d32f -
Update Version n8n vers release @115.2
Verified signature- ai-builder: Fix loading of Data Table nodes for AI Builder. - editor: Compact large ITaskDataConnections before sending to AI Builder. - editor: Keep source control and user area fixed to bottom of sidebar. - Github Node: Fix GitHub node no longer shows repo owner for Get Issues operation. - Update libxml2. ----- - all information https://github.com/n8n-io/n8n/releases/tag/n8n%401.115.275929a9
-
Update Dockerfile
Verified signature3d2f048
-
Update README.md
Verified signatureee90b24
-
Update Dockerfile
Verified signatureb9093fa -
Update Dockerfile
Verified signature9cbaf37