This looks as though you are running keepalived from within a container.
Due to the isolation of containers, applications running within the
container cannot load kernel modules. Once you manually load the module,
keepalived can use the module from within the container.

If keepalived is run natively within the host (i.e. not in a container)
then keepalived can cause the module to be loaded.

The version of keepalived you are using is very old; there is a much
newer version available as a snap.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800159

Title:
  keepalived ip_vs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1800159/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to