[Bug] Self-hosted macos sonoma, aws command not found if runner auto start on login using LaunchAgents with plist defined.

[thinhlv]

Describe the bug env:

• Macos Sonoma on vmware workstation 17
• Self host runner
• Sonoma auto login
• Runner auto start using LaunchAgents for local user (~/Library/LaunchAgents)

The aws command not found if the runner is started automatically with macos when login (login items). If we start the runner manually using run.sh, then the aws works fine.

To Reproduce Steps to reproduce the behavior:

1. Setup env
2. Repo contains script that use aws commandline
3. Run Github Actions
4. aws command not found error.

Expected behavior The runner can be started automatically when sonoma has been logged in

Runner Version and Platform

actions-runner-osx-x64-2.316.1.tar.gz Macos Sonoma 14.5, Vmware workstation pro 17.5.2 build-23775571

What's not working?

aws command not found when runner auto start with macos. Manual start works fine.

Job Log Output

./ScriptsBuildPipeline/publish-artifacts.sh: line 28: aws: command not found ./ScriptsBuildPipeline/publish-artifacts.sh: line 29: aws: command not found ./ScriptsBuildPipeline/publish-artifacts.sh: line 30: aws: command not found % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 179 0 0 100 179 0 326 --:--:-- --:--:-- --:--:-- 326

[thinhlv]

Manually add required path to the $PATH on runtime if command not found