Execution Profile

garnet-labs/harbor

Recorded at the kernel by Garnetfor commit 94d17ba (merge ref)

Clean-run records/trial

run 44615662137

Execution chains

17 destinations · 6 processes
  • systemd
    • dockerd[2206 · dockerd]
      • registry-1.docker.io100.50.49.211:443 (https) · tcp
      • auth.docker.io172.64.144.78:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • production.cloudfront.docker.com3.169.173.111:443 (https) · tcpalso recorded: d3ipk8a4rcghwr.cloudfront.net
      • d3ipk8a4rcghwr.cloudfront.net3.169.173.21:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.100:53 (dns) · udp(dns resolver)
    • dns-resolver[2188 · dns-resolver]
      • localhost127.0.0.2:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1438 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[2443 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • hosted-compute-agent[2579 · hosted-compute-agent]
      • 20.75.202.224:443 (https) · tcp
    • systemd-networkd[740 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/harbor
WorkflowClean-run records
Jobtrial
Profile UUID01a1f5a6-128d-7e6b-8f51-db52fe25f27e
Refrefs/pull/5/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.