Containerd service: don't exec modprobe overlay about puppetlabs-kubernetes HOT 6 CLOSED

We run this code in vagrant a lot, which has that fact set to true, and don't get this error. I'm not aware that the version of docker you're running is officially supported in 1.11.0 either

from puppetlabs-kubernetes.

@davejrt thank you for your answer.
are you also using containerd as runtime instead of docker?
which kind of virtualization is vagrant using?

there is actually no code in the manifests, which take care of is_virtual.
That was my proposal how to fix the issue :)

from puppetlabs-kubernetes.

I'm confused, are you using docker or containerd as the runtime? You've pasted in an unsupported docker version above.

Can you provide more information about the environment you're seeing this issue on so we can determine whether or not this isn't isolated to your combination of software versions and virutal environment.

from puppetlabs-kubernetes.

@davejrt: I'm using containerd as runtime. Sorry, for the confusion. I've missed the version command there for containerd (I've updated the initial report now)

Environment:
3 bare metal servers with:

• Kernel 4.17 (linux-image-4.17.0-0.bpo.1-amd64)
• Debian Stretch (9.5)
• LXC 2.0.7-2+deb9u2
• lxcfs 2.0.7-1

The Kubernetes controllers are running inside a LXC container on each host.
Every bare metal (host) has 1x controller (lxc container) 1x worker (2nd container):
$ lxc-ls

kube-controller2 
kube-worker2  

with the relevant kubernetes containers lxc config:

lxc.include = /usr/share/lxc/config/nesting.conf
lxc.include = /usr/share/lxc/config/debian.common.conf
lxc.mount.auto=proc:rw sys:rw
lxc.aa_profile=unconfined
lxc.cgroup.devices.allow=a

(apparmor disabled / unconfined)

Networking: weave

To point out: the issue is the modprobe command on a lxc guest-machine.
This should never work, because it would be a huge security issue if lxc guests could load kernel module on the host (lxc machines share the kernel with the host)

from puppetlabs-kubernetes.

@khaefeli I have left comments on your pr #147

from puppetlabs-kubernetes.

Closing as this issue is beyond the scope of this module

from puppetlabs-kubernetes.