I am curious if there would be any reason I could not set up keepalived in a Ubuntu 24.04 VM on scale?
I am currently attempting to set up a backup pihole server with a vip using keepalived and am getting an error when attempting to start the service after configuring it stating
Aug 16 21:42:28 pihole01 systemd[1]: Starting keepalived.service - Keepalive Daemon (LVS and VRRP)...
Aug 16 21:42:28 pihole01 Keepalived[37731]: Starting Keepalived v2.2.8 (04/04,2023), git commit v2.2.7-154-g292b299e+
Aug 16 21:42:28 pihole01 Keepalived[37731]: Running on Linux 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 (built for>
Aug 16 21:42:28 pihole01 Keepalived[37731]: Command line: '/usr/sbin/keepalived' '--dont-fork'
Aug 16 21:42:28 pihole01 Keepalived[37731]: Configuration file /etc/keepalived/keepalived.conf
Aug 16 21:42:28 pihole01 Keepalived[37731]: daemon is already running
Aug 16 21:42:28 pihole01 systemd[1]: keepalived.service: Failed with result 'protocol'.
Aug 16 21:42:28 pihole01 systemd[1]: Failed to start keepalived.service - Keepalive Daemon (LVS and VRRP).
I have set this up using 2 VMs in proxmox and everything worked but if I try this in Scale I get the above. The only differences I can think of are that the VM in proxmox are using a cloud-init image and the one on scale is using the normal ubuntu image and the networking in scale is also handled differently. The networking in Scale I have setup with a bridge and attached the VM to the bridge.