Hello, there's issues running both TREK (and beszel?) once tailscale plugin is enabled. Container: mauriceboe/trek (TREK travel planner app) Issue: Enabling "Use Tailscale" on this container causes the Tailscale Unraid Docker Hook to throw a syntax error immediately after successful auth, and the container's actual app process never starts — it hangs on a "Press ANY KEY to close this window" prompt (no TTY available in Docker, so it hangs forever and the container shows red/failed). Suspected cause: The container's Dockerfile CMD is a compound shell script (does a file-existence validation with if [ ... ]; then ... fi, then drops privileges via gosu node and execs the Node app). It looks like the Tailscale hook script tries to eval this original CMD when handing off after Tailscale setup, and chokes on the embedded if/then block — likely a quoting issue in how the hook captures/re-runs the image's original entrypoint/CMD. Container's actual Dockerfile ENTRYPOINT/CMD for reference: ENTRYPOINT ["dumb-init", "--"] CMD ["sh", "-c", "if [ ! -f /app/server/dist/index.js ] || [ ! -d /app/node_modules/tsconfig-paths ]; then echo 'FATAL: TREK application files are missing from the image.'; ...; exit 1; fi; chown -R node:node /app/data /app/uploads 2>/dev/null || true; cd /app/server && exec gosu node node --require tsconfig-paths/register dist/index.js"]