Reaper doesn't look for supercronic in PATH

[atesca09]

Since #172 in v0.22.3 I'm getting

time="2024-10-12T08:43:03+02:00" level=info msg="reaping dead processes"
time="2024-10-12T08:43:03+02:00" level=fatal msg="Failed to fork exec: no such file or directory"

I debugged that behavior to

supercronic/reaper.go

Line 34 in cca6b3a

pid, err := syscall.ForkExec(args[0], args, pattrs)

If the current working dir is / but supercronic is installed in a directory included in PATH e.g. /usr/local/bin/supercronic the reaper still tries to execute supercronic from / which doesn't exist there.

[qianlongzt]

I made a fix, you can try it. @atesca09

#178

[atesca09]

Thanks for the prompt fix! I've tested the changes, and it works for me now.

[Etheonor]

Same issue using Supercronic on a wolfi docker image