Closed utkuozdemir closed 2 months ago
The root cause is that image is pulled and cached in the system containerd in memory (in tmpfs
).
So rebooting a node is enough as a workaround.
The proper fix is to pull the image always while processing the upgrade API request, but use the cached image when running the actual upgrade.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
Bug Report
Description
talosctl upgrade --image some:image
with an invalid installer image.docker push some:image
talosctl upgrade --image some:image
again, it will not re-pull the image and keep failing.We can introduce a flag to the
upgrade
command like--force-pull
to enforce pulling of image.Logs