I want to provide additional context for the issue I reported with Tailscale.
Production confirmation
For reference, I am running Tailscale in production on Fedora CoreOS using a Podman Quadlet setup, and it is working correctly there without issues.
This makes me think the problem is likely specific to the RPM/systemd integration in EPEL rather than Tailscale itself.
From journalctl on Rocky 9:
tailscaled does not take non-flag arguments: [""]
tailscaled.service: Main process exited, code=exited, status=1/FAILURE
Start request repeated too quickly
Failed to start Tailscale node agent
It would be helpful to check the systemd service definition / RPM packaging for any empty or incorrectly templated argument being passed to the daemon.
This update has been submitted for testing by jonathanspw.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
jonathanspw edited this update.
This update can be pushed to stable now if the maintainer wishes
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
I want to provide additional context for the issue I reported with Tailscale.
Production confirmation
For reference, I am running Tailscale in production on Fedora CoreOS using a Podman Quadlet setup, and it is working correctly there without issues.
This makes me think the problem is likely specific to the RPM/systemd integration in EPEL rather than Tailscale itself.
From journalctl on Rocky 9:
tailscaled does not take non-flag arguments: [""] tailscaled.service: Main process exited, code=exited, status=1/FAILURE Start request repeated too quickly Failed to start Tailscale node agent
It would be helpful to check the systemd service definition / RPM packaging for any empty or incorrectly templated argument being passed to the daemon.