So I have tried downloading devuan/excalibur/amd64 and devuan/daedalus/amd64 right now and they both return 502 Bad Gateway (nginx) error.
Before that, about 8 months ago, I tried downloading gentoo amd64 and the image was totally borked, didn’t work at all, did not start/boot.
I think the distrobuilder might have some serious issues, my suspicion would be that the issues could be related to building distros without systemd, because I try to use no-systemd distros and they always fail somehow when I try to use them with incus.
Are you still getting this behavior? We operate a global network of mirrors/proxies for the image server, so issues tend to be pretty location dependent.
That said our global monitoring hasn’t seen any issue in the past couple of days:
Every single image we produce gets tested to ensure it boots, gets IPv4 and IPv6 connectivity and functional DNS. An image cannot appear on the image server unless those tests have passed.
That doesn’t always translate on a guarantee that it will work on your system however as local firewalls, kernel and OS configuration can affect the behavior of containers, but in general, anything you find on our image servers, whether container or VM images will have been tested with the latest stable Incus release on a Debian 13 system.
Hi friends; not sure what happened, but I saw a lot of TLS errors in the logs. I ran certbot renew --force-renewal on the Frankfurt mirror and that seems to have resolved it! Apologies for the glitch.
Thanks for the link; I think there is still a problem I’ll need to resolve with the upstream mirror configuration; but I worked around it and can fetch this URL now. How does it look on your side? I haven’t seen errors in the log in awhile.