Reactor Scram
Reactor Scram
Yeah should be good. I think they're failing because my new code is looking for `firezone-headless-client` and the old Docker images are built with `firezone-linux-client`. But it should not affect...
Will look into it after #4899 I thought maybe `systemctl start` is returning before our tunnel interface is all the way up. When it passes, this `resolvectl dns tun-firezone` prints...
Happened again, but `debug_exit` didn't do what I needed: https://github.com/firezone/firezone/actions/runs/9009905220/job/24755105430
Still happening. https://github.com/firezone/firezone/actions/runs/9290693824/job/25567691838 PR #5111 will move the systemd notification up to the Client so maybe that will give us more control over it.
Another replication https://github.com/firezone/firezone/actions/runs/9469788060/job/26089691139 In this case the DNS didn't get controlled even though our logs indicate we thought it had https://github.com/firezone/firezone/actions/runs/9469788060/job/26089691139#step:6:93
Still happening - #5911 This call to `sd_notify` happens way too early: https://github.com/firezone/firezone/blob/bf693ad83f2fedf2380a843311c05538318b9598/rust/headless-client/src/standalone.rs#L186 That may not be the only root cause, but it's not helping anything.
https://github.com/firezone/firezone/actions/runs/10068439728/job/27834479145
https://github.com/firezone/firezone/actions/runs/10080667883/job/27871200510
That PR may not have `main` merged
#6026 might have fixed it. It merged into `main` 2 days after Jamil's last comment, so that could explain it