fix(cup): stopgap n8n exclude to stop crash-loop (pending upstream #172) - #6
Closed
atomdeniz wants to merge 1 commit into
Closed
fix(cup): stopgap n8n exclude to stop crash-loop (pending upstream #172)#6atomdeniz wants to merge 1 commit into
atomdeniz wants to merge 1 commit into
Conversation
Cup exit(1)'s on an unexpected registry HEAD status, so docker.n8n.io's 429s crash-loop `cup serve` (dozens of restarts, dashboard down; the restarts sustain the rate limit). Exclude n8n from the scan as a stopgap so a cup deploy can't reintroduce the loop. Upstream fix submitted (sergi0g/cup#172, error! -> warn+Err). Remove this line once running the fixed release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
Author
|
Vazgeçildi — kapatıyorum. Canlı sunucudaki n8n-exclude stopgap duruyor, cup güvende. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docker.n8n.io/n8nio/n8nto cup'simages.excludeas a temporary stopgap.Why
Cup's
serveruns its image scan before binding the HTTP server, andClient::requestcallserror!→std::process::exit(1)on an unexpected registry status.docker.n8n.io(n8n's registry) returned429 Too Many Requests, so cup exited on the startup scan and — underrestart: unless-stopped— crash-looped (68 restarts observed), with each restart re-issuing the request and sustaining the rate limit. The whole cup dashboard was down.The server was recovered by excluding n8n live; this commit makes that durable so a
--tags cupdeploy can't reintroduce the loop while the real fix lands.Real fix
Submitted upstream: sergi0g/cup#172 (make unexpected statuses non-fatal —
warn+Errlike the existing 404/401/403/502 branches). Once a cup release includes it:cup_versioninroles/cup/defaults/main.yml.docker.n8n.io/n8nio/n8nexclude line here.Draft until then.
🤖 Generated with Claude Code