Composite actions which contains external bash script doesn't run if the jobs are executed with container

[girishenoy2003]

Bug!!!

I am trying to create my own composite action and run in my workflow as described here

When I run my workflow job with container then the bash script then the bash script is not accessible to run.
The error in the logs I see as:

/__w/_temp/75ecb274-82d9-459d-8632-54e0099fe49e.sh: line 1: /home/xxx/actions-runner/_work/_actions/abc/ooo-action/v1.0/deploy.sh: No such file or directory
Error: Process completed with exit code 127.

But on the other hand, if I see in the runner, the script exists in the specified path.

To Reproduce
Steps to reproduce the behavior:

1. Setup the composite action as described here
2. Write your workflow to run the action but run the jobs on container

runs-on: [self-hosted]    
    container: 
      image: myregistry/xxx/abc/abc-image:1.0
      credentials:
        username: ${{ github.actor }}
        password: ${{ secrets.GITHUB_TOKEN }}

3. The action will fail

Expected behavior
Bash script in the composite action should have been executed but it resulted in error stating there is no such file.

Runner Version and Platform

Runner version - 2.278.0
Running on Linux - x64

What's not working?

The script in composite action is not running with below error:

/__w/_temp/75ecb274-82d9-459d-8632-54e0099fe49e.sh: line 1: /home/xxx/actions-runner/_work/_actions/abc/ooo-action/v1.0/deploy.sh: No such file or directory
Error: Process completed with exit code 127.

[nikola-jokic]

Hi @girishenoy2003,

Just to let you know that we created a PR fixing your issue. This should be resolved once the PR is approved and merged 😁

[nikola-jokic]

Hey @girishenoy2003,

While going through the older issues, I noticed this one #716. So this is a duplicate and I will close this one here. I linked the PR to the older issue as well so you can track it there 😊