Skip to content

DNS resolution fails in podman containers #559

@robert-cronin

Description

@robert-cronin

I am encountering an issue with DNS resolution inside podman containers after the step-security/harden-runner step, specifically the containers are unable to resolve certain domain names like security.debian.org. I've put together a minimal repro that can be found here: https://github.com/robert-cronin/podman-in-harden-runner

I ran two workflows with the only difference being the step-security/harden-runner step removed to make sure I wasn't missing something with podman:

  1. With harden-runner step: https://github.com/robert-cronin/podman-in-harden-runner/actions/runs/15844352622/job/44662966262
  2. Without harden-runner step: https://github.com/robert-cronin/podman-in-harden-runner/actions/runs/15844357377/job/44662983981

I could be missing a step in configuring the runner, so any guidance would also be appreciated. Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions