kadinsayani
commented
1 day ago The issue is in the images_aliases table. When a POST request is made to /1.0/images/aliases, the image_id column is overwritten.
kadinsayani@devbox:~/canonical/lxd$ lxc image copy ubuntu:jammy local: --copy-aliases --vm
Image copied successfully!
kadinsayani@devbox:~/canonical/lxd$ lxd sql global 'select * from images_aliases'
+----+-------------+----------+-------------+------------+
| id | name | image_id | description | project_id |
+----+-------------+----------+-------------+------------+
| 31 | 22.04 | 15 | | 1 |
| 32 | 22.04/amd64 | 15 | | 1 |
| 33 | j | 15 | | 1 |
| 34 | j/amd64 | 15 | | 1 |
| 35 | jammy | 15 | | 1 |
| 36 | jammy/amd64 | 15 | | 1 |
+----+-------------+----------+-------------+------------+
kadinsayani@devbox:~/canonical/lxd$ lxc image copy ubuntu:jammy local: --copy-aliases
Image copied successfully!
kadinsayani@devbox:~/canonical/lxd$ lxd sql global 'select * from images_aliases'
+----+-------------+----------+-------------+------------+
| id | name | image_id | description | project_id |
+----+-------------+----------+-------------+------------+
| 37 | 22.04 | 10 | | 1 |
| 38 | 22.04/amd64 | 10 | | 1 |
| 39 | j | 10 | | 1 |
| 40 | j/amd64 | 10 | | 1 |
| 41 | jammy | 10 | | 1 |
| 42 | jammy/amd64 | 10 | | 1 |
+----+-------------+----------+-------------+------------+I see two options forward:
1) Separate images_aliases into two distinct tables, container_images_aliases and vm_images_aliases; or
2) Separate the image_id column into two distinct columns, container_image_id and vm_image_id (less overhead with this option).
In either case, an alias with the same name could belong to both a container and VM.
Which option would be preferable? cc. @tomponline @hamistao
tomponline
hamistao
DanielDewberry
Required information
Distribution:
KubuntuDistribution version:24.04.1The output of
snap list --all lxd core20 core22 core24 snapd:The output of
lxc info:Issue description
Copied from https://discourse.ubuntu.com/t/unexpected-behaviour-with-lxc-image-copy-copy-alises/47529?u=dwd-daniel, as requested.
I think that the aliases should be copied to the local storage, and should not be unique across instance types. That is to say, both a VM and Container image should be able to have the
jammyornoblealias.Acquring the images: order 1
Issuing
I see the following images are stored:
Notice that the alias is set for the VMs, which are the second of the container/ VM aquisitions.
Acquring the images: order 2
If I switch the order of the Jammy container & VM acquisition, having already executed the previous command:
I see this:
The Jammy container image, which was acquired after the Jammy VM image, owns the alias.
Observation vs expectation
The aliases are not copied and preserved for each image, they seem to be required to one image, irrespective of image type. I expected each image to retain its aliases, and the
--vmswitch to be used as a way to discerne between the container and VMs images.We can see the aliases exist on the remote:
Attempting to set local aliases
If I attempt to add an alias to the local copy of the Jammy container, I am informed the Jammy alias already exists, which leads me to believe the alias must be, as previously noted, unique to a single image irrespective of the image type.
I can set up my own aliases which correctly categorize the images:
Summary
I think that the aliases should be copied to the local storage, and should not be unique across instance types. That is to say, both a VM and Container image should be able to have the
jammyornoblealias.Best regards
Daniel