Skip to content

Access your docker socket safely as read-only, rootless and distroless

active 2025-03-192026-04-10 (UTC)

Partial coverage11,902 / 13,326 hourly files (89%) · 2 absent upstream · 1,420 failed, retryable2025-02-012026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
153
Pushes
11
Pull requests
0
Issues
10
Stars
99
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 388 days from 2025-03-19 to 2026-04-10. Pushes: 11 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 10 total, peak 2 in a day. Comments: 18 total, peak 3 in a day. Stars: 99 total, peak 6 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
11notes15608
coltondick7003
github-actions[bot]5500
ElioDiNino4003
Resolude2001
brtwrst1001
amanda-wee1001
mprokopiev1000
wollomatic1001
johnatank1000
thelastblt1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#17brtwrst2026-02-17 12:14
    Read-only tcp socket is available to any container in the same subnet by default
  • Issue comment#1711notes2026-02-17 07:01
    Read-only tcp socket is available to any container in the same subnet by default
  • Issue comment#1711notes2026-02-16 09:32
    Read-only tcp socket is available to any container in the same subnet by default
  • Issue#15mprokopiev2025-11-13 18:46
    Proxy fails to reestablish connection after Docker restart
  • Issue comment#13Resolude2025-10-26 22:39
    Unable to Run on Rootless Docker
  • Issue#13Resolude2025-10-26 05:24
    Unable to Run on Rootless Docker
  • Issue#12thelastblt2025-10-05 04:47
    Inspect Images API Point Blocked
  • Issue comment#10amanda-wee2025-09-25 21:15
    [Bug] Use of closed network connection
  • Issue comment#10ElioDiNino2025-09-07 03:45
    [Bug] Use of closed network connection
  • Issue comment#10ElioDiNino2025-08-21 06:03
    [Bug] Use of closed network connection
  • Issue comment#10wollomatic2025-08-20 17:53
    [Bug] Use of closed network connection
  • Issue comment#10ElioDiNino2025-08-13 00:06
    [Bug] Use of closed network connection
  • Issue comment#1011notes2025-08-12 05:53
    [Bug] Use of closed network connection
  • Issue comment#11coltondick2025-08-09 04:15
    No access to CPU utilization, Memory usage or Network traffic
  • Issue#11coltondick2025-08-09 04:15
    No access to CPU utilization, Memory usage or Network traffic
  • Issue comment#1111notes2025-08-08 05:41
    No access to CPU utilization, Memory usage or Network traffic
  • Issue comment#1011notes2025-08-07 06:32
    [Bug] Use of closed network connection
  • Issue comment#11coltondick2025-08-07 00:04
    No access to CPU utilization, Memory usage or Network traffic
  • Issue#11coltondick2025-08-07 00:04
    No access to CPU utilization, Memory usage or Network traffic
  • Issue comment#11coltondick2025-08-07 00:01
    No access to CPU utilization, Memory usage or Network traffic
  • Issue#11coltondick2025-08-07 00:01
    No access to CPU utilization, Memory usage or Network traffic
  • Issue#11coltondick2025-08-06 23:27
    No access to CPU utilization, Memory usage or Network traffic
  • Issue#10ElioDiNino2025-08-06 13:12
    [Bug] Use of closed network connection
  • Issue comment#911notes2025-08-06 10:23
    New env var for permission control
  • Issue#811notes2025-07-16 09:35
    Proxy fails to reestablish connection after Docker restart

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 99 stars here means stars gained during the window, not the repo's star count.