Container in use errors when updating HA core version or add-ons #3016
Comments
|
Similarly to not being able to update HA, I get errors as per below when trying to update add-ons: |
|
This seems more related to Supervsior, moving. |
|
Another example of trying to update an Add-on this morning: which looks like it fails, however the update seems to go through ok. Unfortunately I can't say the same for HA version updates. |
|
I just tried to update HA from 2021.7.3 to 2021.7.4 and got the below errors, update failed and HA basically didn't come back to life. Supervisor log: HA log: So after rebooting the host I then SSH'd into the system, So then I once again checked the supervisor log: Hopefully something in there can help solve this issue. EDIT: After the above failures I went back in via SSH and repeated the procedure: |
|
Run |
|
I've run a supervisor repair about 4 times now with no change. I'll do it again though anyway. |
|
I ran the repair again and received the below in the supervisor log: I guess now it's a waiting game to see if I can successfully update HA when the next version is released, or when add-ons have an update available. I'll report back soon. |
|
Looks good so far, if you have a snapshot you could do a partial restore of an addon to trigger an update. |
|
I just tried updating ESPhome from 1.20.0 to 1.20.1 and got the usual error again: So the To re-iterate, the error only happens for add-ons that are running. eg: I just successfully updated the ESPhome Beta add-on without any error because it isn't running. The same seems to be the case for HA core, if I stop HA and update via SSH all is fine, it just won't work while HA is running (ie: via the GUI) |
|
Strangely I just managed to update that same ESPhome Add-on (the main, running one) from v1.20.1 to v1.20.2 without the error. However, the add-on was then not running after the update and I was unable to manually start the add-on from the GUI: I had to reboot the host to get it running again. |
|
I just updated the Supervisor from 6.1 to 6.2 (successfully) and then tried to update HA core from 2021.7.4 to 2021.8.7 but got the below errors in the log. So this is still a problem. I tried my usual work-around method of stopping HA via SSH, updating, the starting, but this also failed. After a host reboot I noticed this in the log: |
|
Well I still can't update HA versions while HA is running (ie: through the GUI). The only solution seems to be to SSH in, stop HA, update, restart. This is crazy. Is anyone looking at this? Latest update attempt log: |
|
Updating Supervisor to 2021.09.0 seems to have fixed my issues. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hardware Environment
Home Assistant OS release:
Supervisor logs:
Journal logs:
Kernel logs:
Description of problem:
Whenever I try to update HA Core to a new version I have major issues. I get errors relating to the Container being is use / name already existing. The same happens if I try to update an Add-on which is running.
The only solution (temporary) has been to stop HA (or the add-on), update, then start again. In this case it sometimes works however it also requires a Host Reboot.
The text was updated successfully, but these errors were encountered: