Bug Report: Docker containers attach and remove images after each restart

[gmshiwoge]

OS Version

Description: Debian GNU/Linux 11 (bullseye)

System Information

Linux HomeAssistant 6.1.62-ophub #1 SMP Sat Nov 11 22:50:08 EST 2023 aarch64 GNU/Linux

What happened?

Every time I restart my system, the Home Assistant Supervisor seems to attach and remove Docker images, specifically the image ghcr.io/home-assistant/qemuarm-homeassistant.

Machine Type

qemuarm-64

Installer output

System Configuration: [Provide details about your system configuration]
Steps to Reproduce: [Outline steps to reproduce the issue]
Attempted Solutions: [If you've tried any solutions, list them here]

Relevant log output

nerd.runtime.v2.task/moby/71524578167e933d58d2959d01c29c18e29fcaf21efb0776ec504880942c6e84 pid=7501 runtime=io.containerd.runc.v2
May 15 17:52:57 HomeAssistant systemd-resolved[880]: System hostname changed to 'HomeAssistant'.
May 15 17:52:57 HomeAssistant systemd-resolved[880]: Detected conflict on HomeAssistant IN AAAA fe80::2293:eb5d:f9d:23e6
May 15 17:52:57 HomeAssistant systemd-resolved[880]: Hostname conflict, changing published hostname from 'HomeAssistant' to 'HomeAssistant8'.
May 15 17:52:57 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:52:57.515 INFO (MainThread) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/aarch64-hassio-multicast with version 2024.03.0 - Host
May 15 17:52:57 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:52:57.533 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
May 15 17:52:57 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:52:57.583 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/qemuarm-homeassistant with version 2024.4.1
May 15 17:52:57 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:52:57.615 INFO (SyncWorker_1) [supervisor.docker.manager] Removing image ghcr.io/home-assistant/qemuarm-homeassistant with latest
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service s6rc-oneshot-runner: starting
May 15 17:52:57 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:52:57.629 INFO (SyncWorker_1) [supervisor.docker.manager] Removing image ghcr.io/home-assistant/qemuarm-homeassistant with 2024.4.1
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service s6rc-oneshot-runner successfully started
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service fix-attrs: starting
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service fix-attrs successfully started
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service legacy-cont-init: starting
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service legacy-cont-init successfully started
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service legacy-services: starting
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: services-up: info: copying legacy longrun mdns (no readiness notification)
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: s6-rc: info: service legacy-services successfully started
May 15 17:52:57 HomeAssistant hassio_multicast[1508]: mdns-repeater (6): dev hassio addr 172.30.32.1 mask 255.255.254.0 net 172.30.32.0
May 15 17:53:27 HomeAssistant hassio_supervisor[1508]: 2024-05-15 18:53:27.160 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemuarm-homeassistant with tag 2024.4.1.
May 15 17:53:32 HomeAssistant chronyd[1255]: Selected source 205.233.73.201 (2.debian.pool.ntp.org)

ADR

• [X] I have read through the ADR and have confirmed that my system is compliant with the requirements
• [X] I understand that if my system is found to not be compliant, my issue will be closed immediately without further investigation

Code of Conduct

• [X] I have read and agree to the Home Assistant Code of Conduct

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.