logrotate of vector-logs permission denied on log sink file about dokku HOT 5 OPEN

With our current create setup in the logrotate config, we need to be able to signal to vector to reload files. Without doing so, vector probably "forgets" to which file it is writing to and just writes into the void/weird file descriptor pointing at a now sorta non-existent file. Unfortunately, the File sink doesn't reopen on SIGHUP, so this isn't possible (vectordotdev/vector#12823).

I wonder if we should be using copytruncate instead of create. This is lossy but I think fine based on how the dokku log files are used (sparingly, if at all). For the vector use case, copytruncate would probably be fine since we're also assuming the logs can be lost (they aren't being shipped to another server after all).

I think if the logrotate config drops the su directive and uses copyrotate instead of create, this should all just work?

from dokku.