Runner not passing input params correctly to container hook #70488
-
Select Topic AreaBug BodyHello, I am experiencing a weird situation when using the runner-container-hooks with a self hosted runner: I installed the Github runner on a fresh Ubuntu 22.04 server with Docker and created a simple workflow: name: Hello Docker
on:
workflow_dispatch:
jobs:
hello-world:
runs-on: [self-hosted]
steps:
- uses: actions/hello-world-docker-action@main
with:
who-to-greet: 'Mona the Octocat'As expected, the job displays the correct message: Then I downloaded the latest release (0.4.0) of the docker runner-container-hook and put the path to the I then did a little bit of debugging, by adding a debug log to the run function of the hook to output the input parameters: async function run(): Promise<void> {
try {
checkEnvironment()
const input = await getInputFromStdin()
// added debug message
core.debug(`Hook input: ${JSON.stringify(input, null, 4)}`)
// ... rest of the fileThe output is very interesting, instead of one element in the I think the problem might be that the runner applications does not pass the input to the hook correctly. I would be glad to receive some help on this topic because I have to customize the "docker run" command line statements and therefore use the hook. Thanks in advance! 🙏🏻 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Yes, i am also interested in a fix! :) |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone 👋 This should be fixed with this PR |
Beta Was this translation helpful? Give feedback.



Hey everyone 👋 This should be fixed with this PR☺️