I thought that it actually may make more sense to run Rancher and my Docker inside an LXC container rather than on the initial host itself.
The container provides me still with near to physical host performance but I am able to start and stop on demand and allocate resources for more docker apps as needed without impacting other guests.
A default LXC does not allow docker to run inside. In order to do so, once the container has been created (for example CT100) I had to:
where I see my lxc container configurations. Stop the container in question, and vi the config file
it will look a bit like this where all I did was to add the part after “#insert docker part below”
arch: amd64 cores: 1 hostname: RancherServer memory: 3088 net0: name=eth0,bridge=vmbr0,gw=xxx.xxx.xx.x,hwaddr=xx:xx:xx:xx:xx:xx,ip=xxx.xxx.xx.xx/24,type=veth onboot: 0 ostype: ubuntu rootfs: local-zfs:subvol-100-disk-1,size=30G swap: 512 #insert docker part below lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow: a lxc.cap.drop:
replaced the old
lxc.aa_profile: unconfined with the new lxc.apparmor.profile: unconfined
Save and then start the container.
You can now login to the container and install docker and or Rancher as per guide here