actions / actions/runner

Missing GITHUB_EVENT_PATH GITHUB Self_hosted_runner

Open
#1,898 15 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I am observing the following error with one in self hosted runner using docker in docker.

Describe the bug
The /github/workflow folder exists, but whatever process is supposed to be adding the event.json
event data doesn't appear to be happening.

To Reproduce
Steps to reproduce the behavior:
The issue is specifically with the following actions:
mb2dev/github-action-comment-pull-request@1.0.0

It ends up giving this following error
GITHUB_EVENT_PATH /github/workflow/event.json does not exist Error: No pull request found.

Expected behavior
The task runs without error and generates my env variables

Runner Version and Platform

GH_RUNNER_VERSION=2.286.1

OS of the machine running the runner?
ubuntu:20.04

What's not working?

Please include error messages and screenshots.

Job Log Output

Run mb2dev/github-action-comment-pull-request@1.0.0 with: message: Docker image created for this PR: UL-10353_gh-self-hosted-f8dfd51 GITHUB_TOKEN: *** env: IMAGE_NAME: eu.gcr.io/XXXXXXXX[2](https://github.com/XXXXXX/XXXXXXX/runs/XXXXXXXX?check_suite_focus=true#step:7:2)14/XXXXXXX-XXXXXXX /usr/bin/docker run --name e5d445f1dcbebb98b4f48bf55458[3](https://github.com/XXXXXXX/XXXXXXX-XXXXXXX/runs/XXXXXXX?check_suite_focus=true#step:7:3)a83d7a6[4](https://github.com/XXXXXXX/XXXXXXX-XXXXXXX/runs/XXXXXXX?check_suite_focus=true#step:7:4)_0[5](https://github.com/XXXXXXX/XXXXXXX-XXXXXXX/runs/XXXXXXX?check_suite_focus=true#step:7:5)e183 --label 7e5d44 --workdir /github/workspace --rm -e IMAGE_NAME -e INPUT_MESSAGE -e INPUT_GITHUB_TOKEN -e INPUT_REACTIONS -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e ACTIONS_ID_TOKEN_REQUEST_URL -e ACTIONS_ID_TOKEN_REQUEST_TOKEN -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/actions/_work/_temp/_github_home":"/github/home" -v "/home/actions/_work/_temp/_github_workflow":"/github/workflow" -v "/home/actions/_work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/actions/_work/XXXXXXX-XXXXXXX/XXXXXXX-XXXXXXX":"/github/workspace" 7e5d44:5f1dcbebb98b4f48bf554583a83d7a[6](https://github.com/XXXXXXX/XXXXXXX-XXXXXXX/runs/6291362735?check_suite_focus=true#step:7:6)4 "Docker image created for this PR: XXXXXXX-branch-self-hosted-f8dfd51" "***" "" [@octokit/rest] const Octokit = require("@octokit/rest")is deprecated. Useconst { Octokit } = require("@octokit/rest") instead GITHUB_EVENT_PATH /github/workflow/event.json does not exist Error: No pull request found.

.

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

Use the supplied self-hosted Docker-in-Docker reproduction and job log as the starting point; inspect how the runner mounts /github/workflow and supplies GITHUB_EVENT_PATH to container actions. Done when /github/workflow/event.json is present for this case and mb2dev/github-action-comment-pull-request@1.0.0 completes without “No pull request found.”

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.