You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the incus daemon caches the index of the repository but doesn't know when to refresh it. When reading the logs of the nginx server serving the simplestreams repository, i can see the requests for the image, but not for the images.json index.
You can see the sha1 mismatch (500dedd061a0 when listing, 1b46a0dfacf7eedb0bfef3f9a3877b54ed9185c8960de67e1b53d2e0e8d52f91 when fetching)
(I'm going to sleep, hence the very short issue, but feel free to request more info, i'll reply tomorrow :D )
The text was updated successfully, but these errors were encountered:
The Incus daemon caches simplestreams data for up to an hour.
The client on the other hand only caches for 5 minutes.
So incus image list remote: would hit a 5 minutes client cache at ~/.cache/incus/.
On the server side, the equivalent cache is an hour long and stores the files at /var/cache/incus/.
Can you confirm that you are past that 1h cache expiry in your case?
Salamandar
changed the title
incus remote list shows the new image, but incus image copy tries to fetch the old image
Invalidate the repo cache when hitting 404s
Nov 21, 2024
tl;dr :
but :
It looks like the incus daemon caches the index of the repository but doesn't know when to refresh it. When reading the logs of the nginx server serving the simplestreams repository, i can see the requests for the image, but not for the
images.json
index.You can see the sha1 mismatch (500dedd061a0 when listing, 1b46a0dfacf7eedb0bfef3f9a3877b54ed9185c8960de67e1b53d2e0e8d52f91 when fetching)
(I'm going to sleep, hence the very short issue, but feel free to request more info, i'll reply tomorrow :D )
The text was updated successfully, but these errors were encountered: