Skip to content

Docker container action - 'right' way to equivalent a volume? #25637

Discussion options

You must be logged in to vote

When you run a container action (e.g. uses: my/action@tag) the runner runs that container, mounts the job workspace into it, and makes it the working directory of the container. So the code running inside the container has access to the workspace and can copy a file from there to another location inside the container. Though it’d be preferable to just use the file as is, but if you use a 3rd party tool that uses a fixed path copying might be the easiest solution.

Assuming you have a file my/config.conf in your working directory and my/action defines a config input, you could call your action like this:

- uses: my/action@tag
  with:
    config: my/config.conf

The runner defines an INPUT_C…

Replies: 4 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected
Comment options

You must be logged in to vote
2 replies
@hridyeshpant
Comment options

@hridyeshpant
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants