IP_SET modules not included in kernel build, prevents container functionality
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Invalid
|
Undecided
|
Unassigned | ||
linux-kvm (Ubuntu) |
Fix Released
|
Undecided
|
Kamal Mostafa | ||
Bionic |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
I would like to run Ubuntu Minimal Cloud Image as the base OS on which I run Kubernetes and various other containers, but it requires ipset and various kernel modules included in the build. Is there a way to have those added by default, or a documented process for me to modify the kernel on my Minimal Cloud images?
I tried to use kube-router as a routing platform for connecting the containers between Ubuntu hosts, but this requires ipset.
The error from kube-router:
I0921 00:19:45.773157 1 kube-router.go:207] Running /usr/local/
Failed to run kube-router: Failed to create network routing controller: Failed to create ipset set on system: ipset v6.34: Kernel error received: set type not supported
After some digging, it seems I need the following modules at least compiled into the kernel as modules:
root@deva-
CONFIG_IP_SET=y
CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
# CONFIG_
Ubuntu Release:
~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
Any help is greatly appreciated.
Changed in linux-kvm (Ubuntu Xenial): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux-kvm (Ubuntu Bionic): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux-kvm (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Note: The IP_SET_* modules are already enabled in linux-kvm-xenial.