Apparently this only happens after an unclean shutdown of the container, (such as a crash or container-cleanup -fv). Unclear if we can remove the --pid flag to keepalived and still have a working system in the cases of HA. Recommend testing if the file exists, and if it does, delete it at container start time.
Apparently this only happens after an unclean shutdown of the container, (such as a crash or container-cleanup -fv). Unclear if we can remove the --pid flag to keepalived and still have a working system in the cases of HA. Recommend testing if the file exists, and if it does, delete it at container start time.