Installing microk8s in an LXC container

microk8s_in_lxc.md

Installing microk8s in an LXC container

I wanted to run Microk8s on a Proxmox 6 host inside of an LXC container. These are my notes from the journey.

1. Create a privileged LXC container through the Proxmox web interface

• Enable nesting and FUSE
  • In Proxmox UI, select container, then Options > Features > Check nesting and FUSE boxes

2. SSH into the Proxmox host and edit the container's config in /etc/pve/lxc/.conf
   • Add the following lines
     • lxc.apparmor.profile: unconfined
     • lxc.cap.drop:
     • lxc.mount.auto: proc:rw sys:rw
3. Start (or restart) the container
4. SSH into the container and create a symlink for /dev/kmsg, which is missing in Ubuntu 19.10 containers
   • ln -s /dev/console /dev/kmsg
   • Has to be repeated on container reboot, which is annoying.
5. Install snapd: apt install snapd
6. Install microk8s: snap install microk8s --classic

The snap commands may need to be run more than once to get past errors.

Troubleshooting

If you get "cannot change profile for the next exec call: No such file or directory", try running: apparmor_parser -r /var/lib/snapd/apparmor/profiles/*

snap install microk8s --classic

Your original suggestion did not work for me in both debian and ubuntu but was a really good starting place.
The following conf works in both ubuntu and debian

root@ns26031989:~# cat /etc/pve/lxc/107.conf 
arch: amd64
cores: 2
features: mount=fuse,nesting=1
hostname: runUp
memory: 4096
net0: name=eth0,bridge=vmbr0,firewall=1,gw=149.202.93.254,hwaddr=02:00:00:3a:88:6e,ip=178.32.45.21/24,type=veth
ostype: debian
rootfs: local:107/vm-107-disk-0.raw,size=80G
swap: 0
lxc.apparmor.profile: unconfined
lxc.cap.drop: 
lxc.mount.auto: proc:rw sys:rw
lxc.mount.entry: /dev/fuse dev/fuse none bind,create=file 0 0
lxc.mount.entry: /sys/kernel/security sys/kernel/security none bind,create=file 0 0

Excellent work, guys. You saved me hours....Thank you so much. I got one addtion to make, though:
It is important to assign static ip adresses to the container because due to some conflict in the configuration, dhcp does not seem to work anymore.