It would be nice to have snapshots.schedule support the @reboot keyword. Such schedule would mean a snapshot would be taken just before starting the instance.

It would also be nice for the snapshots.expiry to support a syntax like 3@reboot to keep the past 3 snapshots taken before startups. This would likely require the snapshots name to have a snapshots.pattern including the reboot

Cloning a container from /ui/containers copies the mac address for the container.

web6 was created by using lxc copy web5 web6 but web5 was created by using the clone option in the UI.

It seems like LXC knows to change mac addresses when starting the new container but the UI j

When using the sample lxdock.yml, I get containers whose names are <project name>-<container name>-<some digits>.

+--------------------------+---------+---------------------+------+------------+-----------+
| myproject-test01-5902851 | RUNNING |                     |      | PERSISTENT | 0         |
+

The following simple source fails for my local system

from pylxd import Client
client = Client()
all_containers = client.containers.all()
print(client.containers.all())

Installation

lxc installation

The preferred method for installing plxd on ubuntu 18.04 LTS is to use snap

% lsb_release -a
No 

Hello,

It would be nice if we could create Windows images for LXD automatically.
Obviously we won't be able to publish such images so we'll have to instruct users
to build them themselves.

For the installation we can extract the wim/esd image using wimapply(from wimlib) + an unattended.xml
And for the customization of the OS we can use cloudbase-init as mentioned here lxc/lxd#6205
This s

Im not particularly well versed in all of LXD networking features (or networking in general), so please advise on what you want to see,

The features should apply to a wide a user base as possible , also be aware of the data that is returned by the LXD Rest API it may not be possible to calculate or perform some of the complex

According to the LXD people over lxc/lxd#6802, the IP in the certificate should not be checked, as it doesn't match their security model. So if I currently (LXD 3.18 or 3.19) I run lxd init and use 127.0.0.1 as the LXD's IP, the certificate is generated with another IP. The proposed fix for that issue is to hardcode 127.0.0.1 for all certificates, rendering all invalid if accessed via another IP

I'm following this for learning purposes. All is well until the first kubeadm command. I am receiving preflight errors regarding memory and swap:

[ERROR Swap]: running with swap on is not supported. Please disable swap 

Maybe add a note about this in the guide? And any pointers on how to go around this "properly"?

LXD is version 4.0 and Kubernetes is at 1.18.1.

Livio

for LXDhub

When I had my LXD remote repository up and running on an instance in the Hetzner Cloud I had 23 application "images" there.

They were:

1. bpm
2. civicrm
3. discourse
4. dokuwiki

Decide what to do about deleting templates. Perhaps first step is to check to see if any containers exist with the template (which is an lxc image), and if none, perform the delete.

If there are some, we can't delete. Display useful error message.

As far as I know, there's no support for /1.0/images/*-requests.

These requests should be supported:

• /1.0/images
  • /1.0/images/<fingerprint>
    * /1.0/images/<fingerprint>/export
    * /1.0/images/<fingerprint>/refresh
    * /1.0/images/<fingerprint>/secret
  • /1.0/images/aliases
    * /1.0/images/aliases/<name>

More information: ht

Image download links are in the setup guide. Feel free to create a pull request if the links are broken

I get this when I start code with ''watch':

  File "lxd_image_server/cli.py", line 66, in update_config
    i.add_watch(Config.path, mask=IN_CLOSE_WRITE)
AttributeError: type object 'Config' has no attribute 'path'

Tested on git master branch code, confight 1.3
Indeed, I do not see any path field on Config object. Also, there should be multiple inotify watch calls, because 'confight

For non Ubuntu/Debian users it would be beneficial if edi could get installed as a snap package.

This page: https://fog05.io/docs/going-deeper/architecture/

talks about:

• Fog Orchestration Engine (FOrcE)
• Fog Infrastructure Manager (FIM)

Maybe I've just not found it yet but is there some documentation about:

• how someone accesses FOrcE and FIM
• how someone uses FOrcE and FIM