Is "lxc image list images: " doesn't return anything - does Canonical have an alternative Image server yet

bmullan · February 27, 2024, 2:05pm

I am on Ubuntu 22.04.4
LXC v5.20

Executing the following now just returns an empty list.

$ lxc image list images:
$

I read the linuxcontainers.org “Important Notice” by Stephane Graber
https://discuss.linuxcontainers.org/t/important-notice-for-lxd-users-image-server/18479

where he says:

The Linux Containers project has made the decision to phase out access to our image server for LXD users. We realize that this may cause significant impact on the LXD user base and so have opted for a progressive phase-out matching those users’ ability to migrate to Incus.

Does Canonical have an alternative already?
If so, the LXD documentation needs to be update as to how to use it as its still talking about use of

$ lxc image list

bmullan · February 27, 2024, 2:28pm

Never mind… I just found this post about the work on the new Canonical Image server:

ru-fu · February 27, 2024, 2:30pm

lxc image list uses the default remote (usually local). You can specify other remotes (see Remote image servers), so for example: lxc image list ubuntu:

tomp · February 27, 2024, 2:42pm

The images: remote was removed as a default remote in the lxc tool in LXD 5.20 onwards.

bmullan · February 27, 2024, 4:23pm

ok I knew that and I can see the opsmaru images but I couldn’t launch even an ubuntu 22.04 image.
I first set opsmaru to my default:

$ lxc remote switch opsmaru

as I kept getting:

$ lxc launch ubuntu:22.04 test
Error: The remote isn’t a private LXD server

So I removed the the opsmaru remote and made “ubuntu” my default.

and I still see…

$ lxc launch ubuntu:22.04 test
Error: The remote isn’t a private LXD server

Now I can not even execute:

$ lxc ls
Error: The remote isn’t a private LXD server

As of now I can’t even start my previously existing LXD VMs and Containers.

Any ideas?

zacksiri · February 27, 2024, 4:31pm

@bmullan

Once you’ve added opsmaru to your remote, you can launch images using:

lxc launch opsmaru:ubuntu/jammy test-ubuntu-01

or 

lxc launch opsmaru:ubuntu/22.04 test-ubuntu-02

List all images using

lxc image list opsmaru:

The : at the end is important. Notice the alias names

zacksiri@ubuntu:~$ lxc image list opsmaru:
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
|            ALIAS            | FINGERPRINT  | PUBLIC |            DESCRIPTION             | ARCHITECTURE |   TYPE    |   SIZE    |          UPLOAD DATE          |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.16 (3 more)        | d4e280b3b850 | yes    | alpine 3.16 arm64 (20240221-14)    | aarch64      | CONTAINER | 2.28MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.16/amd64 (1 more)  | 4fbbab01353e | yes    | alpine 3.16 amd64 (20240221-14)    | x86_64       | CONTAINER | 2.50MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.17 (3 more)        | 8edf37df13ec | yes    | alpine 3.17 arm64 (20240221-14)    | aarch64      | CONTAINER | 2.70MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.17/amd64 (1 more)  | 099f83764a67 | yes    | alpine 3.17 amd64 (20240221-14)    | x86_64       | CONTAINER | 2.93MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.18 (3 more)        | 7c31777227b0 | yes    | alpine 3.18 arm64 (20240221-14)    | aarch64      | CONTAINER | 2.75MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.18/amd64 (1 more)  | 37062029ee44 | yes    | alpine 3.18 amd64 (20240221-14)    | x86_64       | CONTAINER | 2.94MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.19 (3 more)        | e44e496455f5 | yes    | alpine 3.19 arm64 (20240221-14)    | aarch64      | CONTAINER | 2.72MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/3.19/amd64 (1 more)  | b392f4461aaf | yes    | alpine 3.19 amd64 (20240221-14)    | x86_64       | CONTAINER | 2.92MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/edge (3 more)        | 34b71a8b87ab | yes    | alpine edge arm64 (20240221-14)    | aarch64      | CONTAINER | 2.72MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| alpine/edge/amd64 (1 more)  | 4d7c0a086c41 | yes    | alpine edge amd64 (20240221-14)    | x86_64       | CONTAINER | 2.93MiB   | Feb 21, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| debian/12 (7 more)          | e5e3acfbb5f6 | yes    | debian bookworm arm64 (20240226-3) | aarch64      | CONTAINER | 91.47MiB  | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| debian/12/amd64 (3 more)    | dbf29f7a2c9e | yes    | debian bookworm amd64 (20240226-3) | x86_64       | CONTAINER | 94.47MiB  | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| debian/sid (3 more)         | 8d6700d4714d | yes    | debian sid arm64 (20240226-3)      | aarch64      | CONTAINER | 94.44MiB  | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| debian/sid/amd64 (1 more)   | fd0af2dffa61 | yes    | debian sid amd64 (20240226-3)      | x86_64       | CONTAINER | 97.75MiB  | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| ubuntu/jammy (7 more)       | abc4a19346e7 | yes    | ubuntu jammy arm64 (20240226-6)    | aarch64      | CONTAINER | 113.52MiB | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| ubuntu/jammy/amd64 (3 more) | 18d14ed0f20c | yes    | ubuntu jammy amd64 (20240226-6)    | x86_64       | CONTAINER | 119.70MiB | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| ubuntu/noble (7 more)       | d3700e02dac6 | yes    | ubuntu noble arm64 (20240226-6)    | aarch64      | CONTAINER | 136.38MiB | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+
| ubuntu/noble/amd64 (3 more) | 8e12e99b1af7 | yes    | ubuntu noble amd64 (20240226-6)    | x86_64       | CONTAINER | 141.05MiB | Feb 26, 2024 at 12:00am (UTC) |
+-----------------------------+--------------+--------+------------------------------------+--------------+-----------+-----------+-------------------------------+

Also something to note, we’re working on adding VM images. You can track the progress here it was requested by another member here also.

bmullan · February 27, 2024, 7:47pm

That command does not work for me.

I’ve set OPSMARU to default

Executing even the command example you gave:

$ lxc launch opsmaru:ubuntu/22.04 test-ubuntu-02

I still get get that same error…

$ lxc launch opsmaru:ubuntu/22.04 test
Error: The remote isn’t a private LXD server

Any other ideas are welcome.

zacksiri · February 27, 2024, 11:59pm

Which architecture is your machine running? Can you try running lxc info?

We currently only support aarch64 and x86_64 btw.

bmullan · February 28, 2024, 4:26am

I have to use the " --force-local" option to get “lxc info” to work w/out that error

Here is a link to the PDF of the output of “lxc info”

zacksiri · February 28, 2024, 4:36am

Can you try this:

lxc remote switch local

Then

lxc launch opsmaru:ubuntu/22.04 test-ubuntu-something

I think your remote should stay as local because the opsmaru remote is just an image server it’s not an LXD instance you can control. I think that’s what’s causing your error hence switching back to local as the default and referencing opsmaru:ubuntu/22.04 specifically when launching instances.

I was able replicate your error and the above explanation / solution makes the most sense to me.

bmullan · February 28, 2024, 2:39pm

@zacksiri
Thanks…

lxc remote switch local - got my local LXD working again & I can see/start etc my pre-existing Containers & VMs.

Trying opsmaru I can now launch Containers but I did see opsmaru does not yet have any virtual machine images… just containers so far.

Anyway, thanks alot.
brian

zacksiri · February 28, 2024, 2:55pm

Hey Brian

Glad you got it all working. We’re going to add virtual machine images soon. You can check out this issue https://github.com/upmaru/opsmaru-images/issues/6

tomp · April 4, 2024, 10:57am

The new image server is now available: