cr1st1p / k8s-on-lxd Goto Github PK

sudo lxd init
Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]:
Name of the new storage pool [default=default]:
Name of the storage backend to use (lvm, btrfs, dir) [default=btrfs]:
Create a new BTRFS pool? (yes/no) [default=yes]:
Would you like to use an existing empty block device (e.g. a disk or partition)? (yes/no) [default=no]:
Size in GB of the new loop device (1GB minimum) [default=30GB]:
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]:
What should the new bridge be called? [default=lxdbr0]:
What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
Would you like LXD to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]:

 sudo ./k8s-on-lxd.sh -s
❗WARN: It looks like SWAP is enabled on your system. Kubernetes might be unstable.
You should disable it by running: sudo swapoff -a
For more information, check kubernetes/kubernetes#53533
or try searching the net for: 'kubernetes swap'"
This Kubernetes setup will not run the checks for the swap, but you run this at your own risk.
INFO: checking nf_conntrack hashsize, via 'sudo' call
INFO: Checking for 'dir' type storage
INFO: Creating storage dir of type 'dir' from path /var/lib/lxd/disks/dir
Error: Source path '/var/lib/lxd/disks/dir' is within the LXD directory

This is my first time using lxd so maybe I misconfigured something?

Hi!
I don't sure, that this is issue, but i checked few times, after restart cluster no flannels executables and files on worker nodes.

Not sure why, but if I run this on Ubuntu, after it's run, and the server is restarted, the root filesystem is no longer accessible and I have to re-install Ubuntu.