Skip to content

Eliminate persistent “Redact secrets in logs” warnings by running MCP gateway as runner user#26658

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/fix-eacces-permission-denied-logs
Draft

Eliminate persistent “Redact secrets in logs” warnings by running MCP gateway as runner user#26658
Copilot wants to merge 2 commits intomainfrom
copilot/fix-eacces-permission-denied-logs

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 16, 2026

The agent job was consistently emitting warning annotations during Redact secrets in logs because key MCP log files under /tmp/gh-aw/mcp-logs were not readable by the step user. This caused noisy warning badges and prevented redaction from processing those logs.

  • Runtime ownership fix in generated MCP gateway command

    • Updated workflow generation to run the MCP gateway container with the current runner UID/GID.
    • This ensures logs created through /tmp bind mounts are readable by downstream redaction/upload steps.
  • Coverage for generated command contract

    • Added an integration test asserting the compiled workflow includes the explicit Docker user mapping for MCP gateway startup.
docker run -i --rm --network host --user $(id -u):$(id -g) ...

Copilot AI changed the title [WIP] Fix EACCES permission denied warnings in MCP log files Eliminate persistent “Redact secrets in logs” warnings by running MCP gateway as runner user Apr 16, 2026
Copilot AI requested a review from pelikhan April 16, 2026 15:17
@pelikhan
Copy link
Copy Markdown
Collaborator

@lpcox

@pelikhan pelikhan assigned lpcox and unassigned pelikhan and Copilot Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

agent: "Redact secrets in logs" step emits 3 warnings — EACCES permission denied on MCP log files

3 participants