From cff4df74be433dcf26c195f06e13e0fda15e2368 Mon Sep 17 00:00:00 2001 From: Abdud Dayan Adeeb Date: Wed, 17 Jun 2020 21:21:47 -0400 Subject: [PATCH] run on specific shell --- README.md | 31 ++++++++++++++++++++++++++++--- action.yml | 4 ++++ entrypoint.sh | 2 +- 3 files changed, 33 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 3b03afc..72f7756 100644 --- a/README.md +++ b/README.md @@ -2,11 +2,11 @@ This action targets a very specific use-case that is not currently supported by Github Workflows. This action gives you the capability to run built containers. -Docker already supports running commands inside a docker image. See [jobs..container](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer). But it doesn't give you a clean way to run an image from a private repo or an image built on a previous step. +Docker already supports running commands inside a docker image. See [jobs..container](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer). But it doesn't give you a clean way to run an image from a private repo or an image built by a previous step. ### Example Usage -#### Standard use-case +#### single-line command ```yaml - uses: addnab/docker-run-action@v1 with: @@ -14,7 +14,7 @@ Docker already supports running commands inside a docker image. See [jobs. semicolon_delimited_script -exec docker run $INPUT_OPTIONS $INPUT_IMAGE /bin/sh -c "`cat semicolon_delimited_script`" +exec docker run $INPUT_OPTIONS $INPUT_IMAGE /bin/$INPUT_SHELL -c "`cat semicolon_delimited_script`"