Skip to content

Try using old image name of the Supervisor image (#2111)#2113

Merged
agners merged 2 commits intohome-assistant:devfrom
agners:try-using-legacy-image
Sep 6, 2022
Merged

Try using old image name of the Supervisor image (#2111)#2113
agners merged 2 commits intohome-assistant:devfrom
agners:try-using-legacy-image

Conversation

@agners
Copy link
Member

@agners agners commented Sep 5, 2022

No description provided.

@agners agners added the os label Sep 5, 2022
@agners agners requested a review from pvizeli September 5, 2022 15:21
@agners
Copy link
Member Author

agners commented Sep 5, 2022

Actually I realized that isn't all, as the Container will get recreated. We need to also use it at container creation time.

@agners agners changed the title Try using old image name of the Supervisor image Try using old image name of the Supervisor image (#2111) Sep 5, 2022
@agners
Copy link
Member Author

agners commented Sep 5, 2022

With that, a boot without Internet right after OS update succeeds:

-- Boot f6cfaa57a4c845b1a9d3ca673865a9b5 --
Sep 05 19:59:36 homeassistant systemd[1]: Starting HassOS supervisor...
Sep 05 19:59:36 homeassistant docker[788]: hassio_supervisor
Sep 05 19:59:36 homeassistant systemd[1]: Started HassOS supervisor.
Sep 05 19:59:36 homeassistant hassos-supervisor[919]: [WARNING] Supervisor image missing, trying to use the legacy image name
Sep 05 19:59:36 homeassistant hassos-supervisor[919]: [INFO] Supervisor start script has changed, destroying previous container...
Sep 05 19:59:36 homeassistant hassos-supervisor[964]: hassio_supervisor
Sep 05 19:59:36 homeassistant hassos-supervisor[919]: [INFO] Creating a new Supervisor container...
Sep 05 19:59:36 homeassistant hassos-supervisor[972]: 044fa0dc9add1eab01a7009c5bd4d266a43b481cd6afa9390c1dfb0c77be4a34
Sep 05 19:59:36 homeassistant hassos-supervisor[919]: [INFO] Starting the Supervisor...
Sep 05 19:59:36 homeassistant hassos-supervisor[981]: hassio_supervisor

@agners
Copy link
Member Author

agners commented Sep 6, 2022

Discussed with @pvizeli: We could also fix this in Supervisor by tagging the image with the ghcr name and the latest tag. However, we would need to do at least two Supervisor releases to get it out to the installations (one to add the new tagging logic, and then one more so the logic actually applies). It seems that this is the easier way to go about it for now. We can remove the logic in the next major release already again.

@agners agners merged commit cf11b5a into home-assistant:dev Sep 6, 2022
agners added a commit to agners/operating-system that referenced this pull request Sep 8, 2022
home-assistant#2113)

* Try using old image name of the Supervisor image

* Tag the old image with the new name so recreation works
agners added a commit that referenced this pull request Nov 30, 2023
As noted in #2113, we don't need this logic anymore after a major OS
releases. So simply drop the logic to also make the image corruption
detection work again.
agners added a commit that referenced this pull request Nov 30, 2023
* Fix Supervisor image corruption detection

When multiple images match the reference, multiple IDs are passed as a
single argument to docker image rm, leading to an error:
Error response from daemon: page not found

Make sure to pass the ids as separate argument to make the delete work
in any case.

* Cleanup reusing Supervisor from an old/unused reference

As noted in #2113, we don't need this logic anymore after a major OS
releases. So simply drop the logic to also make the image corruption
detection work again.

* Make sure image IDs are sorted to make them unique
agners added a commit that referenced this pull request Dec 4, 2023
* Fix Supervisor image corruption detection

When multiple images match the reference, multiple IDs are passed as a
single argument to docker image rm, leading to an error:
Error response from daemon: page not found

Make sure to pass the ids as separate argument to make the delete work
in any case.

* Cleanup reusing Supervisor from an old/unused reference

As noted in #2113, we don't need this logic anymore after a major OS
releases. So simply drop the logic to also make the image corruption
detection work again.

* Make sure image IDs are sorted to make them unique
darkxst pushed a commit to darkxst/ha-operating-system that referenced this pull request Dec 9, 2023
* Fix Supervisor image corruption detection

When multiple images match the reference, multiple IDs are passed as a
single argument to docker image rm, leading to an error:
Error response from daemon: page not found

Make sure to pass the ids as separate argument to make the delete work
in any case.

* Cleanup reusing Supervisor from an old/unused reference

As noted in home-assistant#2113, we don't need this logic anymore after a major OS
releases. So simply drop the logic to also make the image corruption
detection work again.

* Make sure image IDs are sorted to make them unique
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants