Better explanations of dreamcompute errors

pulling a volume from a running VM tells me i dont have access to do it, when it should say there is an active attachment as well as the name of that attachment.

i should not be able to add an image to the public view if i dont have access, yet i can still attempt it.

if a private image architecture is specified --any architecture-- the system will not boot that image.

I assume you see the errors on We’re aware of these, that’s why we launched it provides a more coherent interface, although it focuses on the most common use cases.