actions / actions/runner

Docker's entrypoint its not been executing when a pipeline starts

Open
#1,964 5 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug keep Runner Bug
Dominant language
C#
Stars
6.3k
Forks
1.4k
Avg merge
1d 16h
Merged PRs (30d)
24

Description

I'm using a custom docker image that executes an ENTRYPOINT in the Dockerfile but when I start a new pipeline it seems like it's not running. I'm trying to override the entrypoint in this way:

    container:
        image: build-box:fedora32
        args: "--entrypoint /usr/local/sbin/entrypoint.sh"

but it didn't work. I also checked the logs and I got this

/usr/local/bin/docker create --name 96440d6a5a1b4327959a908575ac7007_buildboxfedora32_61e57a --label 60e226 --workdir /__w/dummy-parent/dummy-parent --network github_network_a07acb3416474dafa3a215ada707a2ec --entrypoint '/usr/local/sbin/entrypoint.sh' -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work":"/__w" -v "/runner/externals":"/__e":ro -v "/runner/_work/_temp":"/__w/_temp" -v "/runner/_work/_actions":"/__w/_actions" -v "/opt/hostedtoolcache":"/__t" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" build-box:fedora32 "-f" "/dev/null"

Can someone please help me to fix this? According to here: https://docs.github.com/en/enterprise-server@3.2/actions/creating-actions/metadata-syntax-for-github-actions#runsentrypoint, it should be running the ENTRYPOINT on the Dockerfile by default

If you omit entrypoint, the commands you specify in the Docker ENTRYPOINT instruction will execute. The Docker ENTRYPOINT instruction has a shell form and exec form.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the container configuration and the logged docker create command shown in the issue, comparing the requested entrypoint with the final command's entrypoint arguments. Trace the runner's Docker container setup and verify the fix by starting a pipeline where the Dockerfile ENTRYPOINT executes when no override is requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.