The service cannot be started because the conditions for determining the result of the kill command in the start function of the Linux version startup script are incorrect.
Below is the debug log of the script. Do not start the service even if the pid file does not exist.
@bradunity As I noticed later, when using Accelerator with Docker, unity-accelerator-launch set in CMD always has pid 1, so it will be caught in multiple launch inspection. This can be avoided by adding a comparison with your own pid.
~ # diff -u /opt/Unity/accelerator/unity-accelerator-launch.orig /opt/Unity/accelerator/unity-accelerator-launch
--- /opt/Unity/accelerator/unity-accelerator-launch.orig
+++ /opt/Unity/accelerator/unity-accelerator-launch
@@ -22,7 +22,7 @@
export PATH
fi
pid="$(cat "$PIDFN" 2>/dev/null)"
- if ! kill -0 $pid 2>/dev/null; then
+ if [ "$" == "$pid" ] || ! kill -0 $pid 2>/dev/null; then
if $FOREGROUND; then
echo "$" > "$PIDFN"
exec "$AGENT" run --persist "$STORAGEDIR" >"${LOGFN}" 2>&1