Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 3
Message 1 of 5

Input parameters are not passed to docker entrypoint when action.yaml has .yaml extension

Solved! Go to Solution.

When creating an action using a docker image, if your metadata file is named `action.yaml`, the action appears to work fine in all regards, except that input parameters are not passed to `/usr/bin/docker` as seen below, causing the entrypoint to not receive any arguments.

 

 

lol2.png

 

 

If instead the action's metadata file is named `action.yml`, the parameters will be passed as expected. In the image below, notice how there is a parameter, "bob", passed to /usr/bin/docker.

 

lol3.png

 

 

Repro:

1. Fork https://github.com/actions/hello-world-docker-action

2. In your fork, `git mv action.yml action.yaml` and push the commit

3. Follow https://help.github.com/en/actions/building-actions/creating-a-docker-container-action#testing-out-y... and set the using action to your fork @master.

 

Similar to https://github.community/t5/GitHub-Actions/Actions-input-parameters-are-not-passed-to-images-pulled-...

4 Replies
Highlighted
GitHub Partner
Message 2 of 5

Re: Input parameters are not passed to docker entrypoint when action.yaml has .yaml extension

Thank you for pointing this out. I have directed your feedback to the appropriate engineering team for further evaluation. When they give me any feedback, I will update here at once. 

Highlighted
Solution
GitHub Partner
Message 3 of 5

Re: Input parameters are not passed to docker entrypoint when action.yaml has .yaml extension

@lucianposton The change to support action.yaml is part of 2.165.x runner release which hasn't released to all production Rings. We have scheduled to release to the last Ring tomorrow. Please wait for a few days for the changes can be used. Thank you for your understanding.  

Highlighted
GitHub Partner
Message 4 of 5

Re: Input parameters are not passed to docker entrypoint when action.yaml has .yaml extension

@lucianposton  The change to support action.yaml has released to all production Rings. I tested in my side, the action.yaml could work now. How about yours? 

Highlighted
Copilot Lvl 3
Message 5 of 5

Re: Input parameters are not passed to docker entrypoint when action.yaml has .yaml extension

The issue seems to be resolved. I was unable to reproduce the problem.

 

screenshot-2020-02-26T16:10:57.057Z.png

 

Thanks