creating-a-docker-container-action.md

title	shortTitle	intro	redirect_from	versions	type	topics
Creating a Docker container action	Create a Docker container action	This guide shows you the minimal steps required to build a Docker container action.	/articles/creating-a-docker-container-action /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action /actions/automating-your-workflow-with-github-actions/creating-a-docker-container-action /actions/building-actions/creating-a-docker-container-action /actions/creating-actions/creating-a-docker-container-action	fpt ghes ghec * * *	tutorial	Action development Docker

{% data reusables.actions.enterprise-github-hosted-runners %}

Introduction

In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.

Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.

{% data reusables.actions.self-hosted-runner-reqs-docker %}

{% data reusables.actions.context-injection-warning %}

Prerequisites

• You must create a repository on {% data variables.product.github %} and clone it to your workstation. For more information, see AUTOTITLE and AUTOTITLE.
• If your repository uses {% data variables.large_files.product_name_short %}, you must include the objects in archives of your repository. For more information, see AUTOTITLE.
• You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %}, environment variables and the Docker container filesystem. For more information, see AUTOTITLE and AUTOTITLE.

Creating a Dockerfile

In your new hello-world-docker-action directory, create a new Dockerfile file. Make sure that your filename is capitalized correctly (use a capital D but not a capital f) if you're having issues. For more information, see AUTOTITLE.

Dockerfile

# Container image that runs your codeFROM alpine:3.10 # Copies your code file from your action repository to the filesystem path `/` of the containerCOPY entrypoint.sh /entrypoint.sh # Code file to execute when the docker container starts up (`entrypoint.sh`)ENTRYPOINT ["/entrypoint.sh"]

Creating an action metadata file

Create a new action.yml file in the hello-world-docker-action directory you created above. For more information, see AUTOTITLE.

{% raw %} action.yml

# action.ymlname: 'Hello World'description: 'Greet someone and record the time'inputs: who-to-greet: # id of inputdescription: 'Who to greet'required: truedefault: 'World'outputs: time: # id of outputdescription: 'The time we greeted you'runs: using: 'docker'image: 'Dockerfile'args: - ${{ inputs.who-to-greet }}

{% endraw %}

This metadata defines one who-to-greet input and one time output parameter. To pass inputs to the Docker container, you should declare the input using inputs and pass the input in the args keyword. Everything you include in args is passed to the container, but for better discoverability for users of your action, we recommended using inputs.

{% data variables.product.prodname_dotcom %} will build an image from your Dockerfile, and run commands in a new container using this image.

Writing the action code

You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the who-to-greet input variable to print "Hello [who-to-greet]" in the log file.

Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must write them to the $GITHUB_OUTPUT environment file: echo "<output name>=<value>" >> $GITHUB_OUTPUT. For more information, see AUTOTITLE.

1. Create a new entrypoint.sh file in the hello-world-docker-action directory.

2. Add the following code to your entrypoint.sh file.

   entrypoint.sh

   #!/bin/sh -lecho"Hello $1" time=$(date)echo"time=$time">>$GITHUB_OUTPUT

   If entrypoint.sh executes without any errors, the action's status is set to success. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see AUTOTITLE.

3. Make your entrypoint.sh file executable. Git provides a way to explicitly change the permission mode of a file so that it doesn’t get reset every time there is a clone/fork.

   git add entrypoint.sh git update-index --chmod=+x entrypoint.sh

4. Optionally, to check the permission mode of the file in the git index, run the following command.

   git ls-files --stage entrypoint.sh

   An output like 100755 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 entrypoint.sh means the file has the executable permission. In this example, 755 denotes the executable permission.

Creating a README

To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.

In your hello-world-docker-action directory, create a README.md file that specifies the following information:

• A detailed description of what the action does.
• Required input and output arguments.
• Optional input and output arguments.
• Secrets the action uses.
• Environment variables the action uses.
• An example of how to use your action in a workflow.

README.md

# Hello world docker action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. ## Inputs## `who-to-greet`**Required** The name of the person to greet. Default `"World"`. ## Outputs## `time` The time we greeted you. ## Example usage uses: actions/hello-world-docker-action@v2 with: who-to-greet: 'Mona the Octocat'

Commit, tag, and push your action

From your terminal, commit your action.yml, entrypoint.sh, Dockerfile, and README.md files.

It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see AUTOTITLE.

git add action.yml entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 git push --follow-tags

Testing out your action in a workflow

Now you're ready to test your action out in a workflow.

• When an action is in a private repository, you can control who can access it. For more information, see AUTOTITLE.
• {% ifversion ghes or ghec %}When an action is in an internal repository, you can control who can access it. For more information, see AUTOTITLE.{% else %}When an action is in an internal repository, the action can only be used in workflows in the same repository.{% endif %}
• Public actions can be used by workflows in any repository.

{% data reusables.actions.enterprise-marketplace-actions %}

Example using a public action

The following workflow code uses the completed hello world action in the public actions/hello-world-docker-action repository. Copy the following workflow example code into a .github/workflows/main.yml file, but replace the actions/hello-world-docker-action with your repository and action name. You can also replace the who-to-greet input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see AUTOTITLE. {% endif %}

.github/workflows/main.yml

on: [push]jobs: hello_world_job: runs-on: ubuntu-latestname: A job to say hellosteps: - name: Hello world action stepid: hellouses: actions/hello-world-docker-action@v2with: who-to-greet: 'Mona the Octocat'# Use the output from the `hello` step - name: Get the output timerun: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %}

Example using a private action

Copy the following example workflow code into a .github/workflows/main.yml file in your action's repository. You can also replace the who-to-greet input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}

.github/workflows/main.yml

on: [push]jobs: hello_world_job: runs-on: ubuntu-latestname: A job to say hellosteps: # To use this repository's private action,# you must check out the repository - name: Checkoutuses: {% data reusables.actions.action-checkout %} - name: Hello world action stepuses: ./ # Uses an action in the root directoryid: hellowith: who-to-greet: 'Mona the Octocat'# Use the output from the `hello` step - name: Get the output timerun: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %}

{% data reusables.actions.test-private-action-example %}

Accessing files created by a container action

When a container action runs, it will automatically map the default working directory (GITHUB_WORKSPACE) on the runner with the /github/workspace directory on the container. Any files added to this directory on the container will be available to any subsequent steps in the same job. For example, if you have a container action that builds your project, and you would like to upload the build output as an artifact, you can use the following steps.

workflow.yml

jobs: build: runs-on: ubuntu-lateststeps: - name: Checkoutuses: {% data reusables.actions.action-checkout %}# Output build artifacts to /github/workspace on the container. - name: Containerized Builduses: ./.github/actions/my-container-action - name: Upload Build Artifactsuses: {% data reusables.actions.action-upload-artifact %}with: name: workspace_artifactspath: {% raw %}${{ github.workspace }}{% endraw %}

For more information about uploading build output as an artifact, see AUTOTITLE.

Example Docker container actions on {% data variables.product.prodname_dotcom_the_website %}

You can find many examples of Docker container actions on {% data variables.product.prodname_dotcom_the_website %}.

• github/issue-metrics
• microsoft/infersharpaction
• microsoft/ps-docs