luckberg/unraid-docker-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(12-01): document Unraid update badge limitation

Browse Source 
- Add Known Limitations section to DEPLOY-SUBWORKFLOWS.md
- Document UNR-01: Unraid shows "apply update" after bot updates a container
- Explain root cause: bot bypasses Unraid's XML template system
- Provide workaround: click Apply Update in Unraid (instant, image cached)
- Clarify "Check for Updates" does NOT clear badge, may create new ones
- Mark UNR-01 as complete (documented limitation with workaround)
This commit is contained in:
Lucas Berger
2026-02-08 17:14:58 -05:00
parent e6e5df8754
commit 7601e245a9
2 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/REQUIREMENTS.md
+2 -2
View File
@@ -58,7 +58,7 @@
### Unraid Integration
- [ ] **UNR-01**: After bot updates a container, Unraid UI no longer shows "update available" for that container
- ✓ **UNR-01**: After bot updates a container, Unraid UI no longer shows "update available" for that container — Documented as known limitation with workaround, Phase 12
### Environment & Config
@@ -102,7 +102,7 @@
| BATCH-05 | Phase 11 | Pending |
| BATCH-06 | Phase 11 | Pending |
| BATCH-07 | Phase 11 | Pending |
| UNR-01 | Phase 12 | Pending |
| UNR-01 | Phase 12 | Complete |
| ENV-01 | Phase 12 | Complete |
| ENV-02 | Phase 12 | Complete |
| DEBT-02 | Phase 12 | Complete |
DEPLOY-SUBWORKFLOWS.md
+16
View File
@@ -68,6 +68,22 @@ cp n8n-workflow.json.backup-confirm n8n-workflow.json
Then re-import the restored `n8n-workflow.json` to n8n.
## Known Limitations
### Unraid Update Badges (UNR-01)
After the bot updates a container, Unraid's Docker tab may show "apply update" on the next update check. This is expected behavior.
**Why this happens:** The bot uses the Docker API directly to pull images and recreate containers. Unraid manages containers through its own XML template system and doesn't know the container was updated outside of its control.
**What to do:** Click "Apply Update" in Unraid's Docker tab. It completes instantly because the image is already pulled and cached — Unraid just recreates the container from its template to sync its internal tracking.
**Important:** "Check for Updates" in Unraid does NOT clear an existing badge. It may actually cause a new badge to appear if the bot updated a container that Unraid hadn't checked yet.
**Why not fix programmatically:** Clearing the badge would require calling Unraid's internal web API to "apply" the update through its template system. This adds significant complexity (Unraid web UI access, authentication, template parsing) for a cosmetic issue that takes one click to resolve.
---
## Architecture
```