Some lxd containers don’t initialize networking or host name.
Versions of the related components and OS (frontend, hypervisors, VMs):
One 5.8.3
LXD 3.0.4/stable
Ubuntu 18.04
Steps to reproduce:
Install fedora30 lxd from market place. Instantiate in a priviliged mode or default (unprivileged)
Install kali linux from the same market place
Install debian buster from the same market place
Install ubuntu bionic from the same market place
Current results:
Fedora 30:
Console doesn’t work, hostname doesn’t change to a container name, container start interface eth0 is up but no ip address assigned
Kali:
Console works, hostname doesn’t change to a container name, container start interface eth0 is up but no ip address assigned
Debian Buster:
Console works but not for root, hostname doesn’t change to a container name, container start interface eth0 and IP address assigned
Ubuntu Bionic:
All things work but only in privileged security mode.
Expected results:
Console works for all users
Hostname is properly set
Network is working
All of this, at least 2 and 3 should work consistently in privileged and unprivileged mode.
The container images imported from the marketplace are meant to be run only under privileged mode. The reasoning for this is basically this limitation.
That being said, images that are auto-contextualized when importing are: alpine (andy version), centos 6 and 7, ubuntu and debian (any version), fedora will be added, however kali probably not.
I see that Fedora 30 contextualization has been added to tested list today. How often the images are being rebuilt? Also I tried to remove and reimport debian buster image but I am getting image 6 exist error.
Sorry, answered image in use question myself. I had to remove a container using older image and then remove the image itself. It sounds like a problem though. Let say I use image X 1.0 for lxd and then found out that bug fixed in X 1.1. Even if I use X 1.0 for current containers, shouldn’t I be able to use 1.1 for new ones? From my past I remember that the images can be versioned. When you downloading lxd image for debian buste wouldn’t it be a good idea to based id at least on the current image version? So you can have both X 1.0 and X 1.1 perhaps with the different names that incorporate the version?
I download fedora on 11/14. and use it to run 3 containers. Then on. 11/30 a new fedora image becomes available with feature X. I am trying importing a new lxd image but opennebula tells me that I already have one which it can’t overwrite because it is in use by running containers. Versioning of images would allow to have and use more than one image of the same linux distribution.
Well, the only rename possible is the template name. Maybe adding a way to rename the image will suffice as the initial workaround. The app could, have a name suffix in both the vm template and the app template to specificy, for example, the release date, and that way it would be possible to update without issues.
Could you open a feature request on github for the team to have a nicer time evaluating this ?