You shouldn’t incus remote switch to an image server as otherwise it will try to create the instance on the image server, failing with the error you’re getting.
So run incus remote switch local to be back to your local system.
That said, I expect incus image list ubuntu: to be empty as the Ubuntu image servers don’t publish images with the Incus metadata.
You can manually go to Ubuntu 22.04 LTS (Jammy Jellyfish) release [20240319], then download ubuntu-22.04-server-cloudimg-amd64.squashfs and ubuntu-22.04-server-cloudimg-amd64-lxd.tar.xz and then manually import those locally with:
The incus CLI command is pre-configured with several remote image servers.
However there’s only one: images. (There’s local as well, but that isn’t remote).
When bootstrapping incus, it tells you to try “incus launch images:blah”. However in git, it looks like some of the translations are out of date. For example:
./po/fr.po:"Pour démarrer votre premier conteneur, essayer : lxc launch ubuntu:16.04"
./po/fr.po:#~ "To start your first container, try: lxc launch ubuntu:20.04\n"
./po/fr.po:#~ "Or for a virtual machine: lxc launch ubuntu:20.04 --vm"
./po/fr.po:#~ "Pour démarrer votre premier conteneur, essayer : lxc launch ubuntu:16.04"
./po/fr.po:#~ msgid "To start your first instance, try: lxc launch ubuntu:20.04"
./po/fr.po:#~ "Pour démarrer votre premier conteneur, essayer : lxc launch ubuntu:16.04"
./po/fr.po:#~ " lxc init ubuntu:16.04 u1"
./po/fr.po:#~ " lxc init ubuntu:16.04 u1"
./po/fr.po:#~ " lxc launch ubuntu:16.04 u1"
./po/fr.po:#~ " lxc launch ubuntu:16.04 u1"
./po/fr.po:#~ msgid "To start your first instance, try: lxc launch ubuntu:18.04"
./po/fr.po:#~ "Pour démarrer votre premier conteneur, essayer : lxc launch ubuntu:16.04"