Add label actions for core-issue and docker-corruption#7011
Draft
agners wants to merge 3 commits into
Draft
Conversation
Add the dessant/label-actions workflow, mirroring the setup in the operating-system repository. Two label actions are configured: - core-issue: points the reporter to the Home Assistant Core issue tracker and closes the issue as not planned. - docker-corruption: explains local Docker image storage corruption (checksums are only verified on pull, shared layers defeat delete and re-pull), describes how to recover via backup and reinstall, links the storage reset feature request (#6555), and closes the issue as not planned. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
home-assistant
Bot
added
cla-signed
refactor
Reports like home-assistant/addons#4720 show 0-byte or empty files as the most common symptom of corrupted Docker image storage, so name that first. Drop the ModuleNotFoundError example as it is less common. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Explain that Docker container images are used under the hood, state the recovery steps up front as a clear call to action, and move the Docker internals (checksums only verified on pull, shared layers) into a background section at the end for those familiar with Docker. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
agners
commented
Jul 14, 2026
Member
Author
There was a problem hiding this comment.
Since we have this already in OS, and adding it here too, we should have them centralized in service bot. We probably then can also get rid of the OS label action.
5 tasks
agners
marked this pull request as draft
July 15, 2026 08:30
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.
Proposed change
Introduce the dessant/label-actions workflow to this repository, mirroring the existing setup in the operating-system repository. Applying a configured label to an issue posts a canned reply and closes the issue as not planned.
Two label actions are configured:
ModuleNotFoundErrorfor files missing inside the container, see Supervisor crash loop on container restart — Python 3.14.5 musl build missing importlib.metadata and importlib.resources #6950 for a recent example). The reply explains that Docker verifies image checksums only on pull, why deleting and re-pulling an image does not necessarily help (shared layers), how to recover (backup + reinstall), and links the Docker storage reset feature request Implement command to reset Docker storage #6555.The
core-issueanddocker-corruptionlabels need to be created in this repository for the workflow to be usable.Type of change
Additional information
Checklist
ruff format supervisor tests)If API endpoints or add-on configuration are added/changed: