Comment 1 for bug 2046249

Thanks for the report.

I took a closer look at the AMS logs in VM12, and the earliest entries related to the dangling base instance issue are as follows:

```
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.114456 637614 housekeeper.go:276] Housekeeper: Processing task clmpdni7h686018t8eqg with status error
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.115212 637614 housekeeper.go:276] Housekeeper: Processing task cll5f6a7h686018t8e70 with status error
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.120490 637614 housekeeper.go:276] Housekeeper: Processing task clmpfra7h686018t8es0 with status error
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.122499 637614 housekeeper.go:327] Housekeeper: Container clmpdni7h686018t8eq0 is already marked as failed
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.122703 637614 housekeeper.go:327] Housekeeper: Container cll5f6a7h686018t8e6g is already marked as failed
2024-01-14T14:57:06Z ams.ams[637614]: I0114 14:57:06.123620 637614 housekeeper.go:327] Housekeeper: Container clmpfra7h686018t8erg is already marked as failed

```

The corresponding application deletion logs, which are most likely causing this situation, have been truncated. Until now, I have not found a reliable way to reproduce this problem. Before we address or work around this issue, if the dangling base instances now prevents AMS from scheduling new instances, please refer to the workaround below.

https://discourse.ubuntu.com/t/anbox-container-change-disk-size-doesnt-work/41931/8?u=gary-wzl77

Thanks
Gary