Update n8nio/runners Docker tag to v2.34.2 - #42
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThe Docker Compose configuration updates the ChangesRunner image update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docker-compose.yml`:
- Line 382: Align the n8nio/n8n and n8nio/runners image tags in the Docker
Compose configuration by either updating the main n8nio/n8n image to 2.32.5 or
changing the runner image to 2.32.4; ensure both use the same version.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: dc1a288d-3a71-4d45-ac68-c0d37bfc539c
📒 Files selected for processing (1)
docker-compose.yml
| cap_drop: | ||
| - ALL | ||
| image: n8nio/runners:2.32.4 | ||
| image: n8nio/runners:2.32.5 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== docker-compose.yml around n8n/runner images ==\n'
nl -ba docker-compose.yml | sed -n '300,400p'
printf '\n== search for n8n version guidance in repo ==\n'
rg -n "runner|n8n.*version|same version|protocol incompatibilities|n8nio/n8n|n8nio/runners" -S . || trueRepository: xRahul/Pi-setup
Length of output: 244
🌐 Web query:
n8n runners same version main worker runner protocol incompatibilities docker compose documentation
💡 Result:
When using n8n with external task runners in a Docker Compose environment, maintaining version consistency and proper network configuration is critical to avoiding protocol incompatibilities and connection failures [1][2]. Version Matching The n8nio/runners image version must match the version of the n8nio/n8n image exactly [1][2]. Mismatched versions can lead to protocol incompatibilities in the communication between the task broker (the n8n instance) and the task runner [1][2]. Additionally, when running n8n in queue mode, all main and worker processes must also be running the same version of n8n to ensure cluster stability [3]. Common Incompatibilities and Configuration Requirements - Broker Connection: Task runners must connect to the specific n8n instance acting as the broker (the main n8n instance or specific worker instances, depending on your configuration) [4]. If using Docker Compose, ensure the N8N_RUNNERS_TASK_BROKER_URI environment variable correctly references the service name and the broker port (default 5679), not localhost, to avoid connection resolution errors [5][6]. - Sidecar Topology: In queue mode, each n8n instance (main and worker) that processes tasks generally requires its own dedicated sidecar container for task runners [4][2]. If OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS is set to true, only workers strictly need the runner sidecars; however, if set to false, the main instance also requires one to handle manual executions [4][2]. - Authentication: You must use a consistent N8N_RUNNERS_AUTH_TOKEN shared between the n8n instance and the runner containers [1][2][6]. - Networking: The N8N_RUNNERS_BROKER_LISTEN_ADDRESS must be set to 0.0.0.0 (rather than the default localhost) to allow the broker to accept connections from external sidecar containers in a multi-container Docker environment [1][2][7]. Known Issues Users have historically reported issues where runner containers fail to re-establish communication if the worker container restarts, or where specific n8n releases introduce incompatibilities in the runner image (e.g., related to native addon or Node.js runtime mismatches) [8][9]. Always check the release notes for your specific n8n version, as patches to the main n8n image do not always automatically propagate to the external runners image [8].
Citations:
- 1: https://docs.n8n.io/deploy/host-n8n/configure-n8n/set-up-task-runners
- 2: https://main--n8n-docs.netlify.app/hosting/configuration/task-runners/
- 3: https://github.com/n8n-io/n8n-docs/blob/main/docs/hosting/scaling/queue-mode.md
- 4: https://community.n8n.io/t/remove-task-runner-from-n8nio-n8n-docker-image/237180
- 5: https://community.n8n.io/t/cant-run-task-runner-at-docker/238054?tl=en
- 6: https://community.n8n.io/t/external-task-runner-v2-4-8-error-when-launching-runner-process/259133/3?tl=en
- 7: https://n8n-docs.teamlab.info/hosting/configuration/task-runners/
- 8: https://community.n8n.io/t/psa-v2-8-x-external-task-runner-broken-need-better-qa/274973
- 9: n8n Worker-Runner Connection Loss After Auto-Restart n8n-io/n8n#23447
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== docker-compose.yml slice around runner/main images ==\n'
sed -n '300,400p' docker-compose.yml
printf '\n== all n8nio image tags in docker-compose.yml ==\n'
grep -nE 'n8nio/(n8n|runners):' docker-compose.yml || trueRepository: xRahul/Pi-setup
Length of output: 3485
Keep the n8n and runner images on the same version. n8nio/n8n is still pinned to 2.32.4 while n8nio/runners is 2.32.5; this version skew can break task-runner communication. Update the main image in the same PR, or keep the runner on 2.32.4.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docker-compose.yml` at line 382, Align the n8nio/n8n and n8nio/runners image
tags in the Docker Compose configuration by either updating the main n8nio/n8n
image to 2.32.5 or changing the runner image to 2.32.4; ensure both use the same
version.
8a55d11 to
61ca0f2
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docker-compose.yml`:
- Line 382: Update the n8nio/runners image tag in the Docker Compose
configuration to match the n8nio/n8n image tag, 2.32.4, unless documented
compatibility explicitly supports the current cross-version pairing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: c4660cfc-b8bc-4012-b3a9-59463255c6ad
📒 Files selected for processing (1)
docker-compose.yml
| cap_drop: | ||
| - ALL | ||
| image: n8nio/runners:2.32.4 | ||
| image: n8nio/runners:2.33.0 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major
Keep the n8n and runner images on the same version.
n8nio/n8n remains pinned to 2.32.4 at Line 317, while this change sets n8nio/runners to 2.33.0. Align both tags, or verify that this cross-version combination is explicitly supported before merging.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docker-compose.yml` at line 382, Update the n8nio/runners image tag in the
Docker Compose configuration to match the n8nio/n8n image tag, 2.32.4, unless
documented compatibility explicitly supports the current cross-version pairing.
61ca0f2 to
7821a7b
Compare
7821a7b to
c3312c5
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docker-compose.yml`:
- Line 382: Align the runner image tag in the Docker Compose configuration with
the n8nio/n8n image tag, using 2.32.4 for both unless explicit compatibility
verification supports the newer runner version.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| cap_drop: | ||
| - ALL | ||
| image: n8nio/runners:2.32.4 | ||
| image: n8nio/runners:2.33.2 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major
Keep the n8n and runner images on the same version.
n8nio/n8n remains pinned to 2.32.4 at Line 317, while this change sets the runner to 2.33.2. Align both tags, or verify that this cross-version pairing is explicitly supported before merging; n8n recommends upgrading main, worker, and runner components together to avoid protocol incompatibilities. (docs.n8n.io)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docker-compose.yml` at line 382, Align the runner image tag in the Docker
Compose configuration with the n8nio/n8n image tag, using 2.32.4 for both unless
explicit compatibility verification supports the newer runner version.
Source: MCP tools
c3312c5 to
fbca7df
Compare
c04ba78 to
484bffd
Compare
484bffd to
7ec7c98
Compare
This PR contains the following updates:
2.32.4→2.34.2Release Notes
n8n-io/n8n (n8nio/runners)
v2.34.0Bug Fixes
causeon execution errors (#35216) (0d4c3a7)Features
Performance Improvements
v2.33.5Bug Fixes
v2.33.4Bug Fixes
v2.33.3Bug Fixes
v2.33.2Bug Fixes
v2.33.1Features
v2.33.0Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.