With the second patch below, I confirm that the ‘wpa-supplicant’ starts correctly. We can see in /var/log/messages that ‘read-pid-file’ first reads the empty string from /var/run/wpa_supplicant.pid, then tries again, and gets a valid PID on the second attempt. It’s surprising that the timing is always like that, and only on the bare metal, but that’s the way it is. It’d be great if you could do some testing with the patch below. Then I guess we’ll push a Shepherd release with this fix. I wonder if this could also explain . Thanks, Ludo’.