What the internet is saying about Docker

What the internet is saying about "Docker containers 2025"

The evidence is thin and noisy. Several items (e.g. [13]–[18]) appear to match only because "2025" is in the PR or issue number, and their visible text has no Docker content. I leave them out of the sections below.

🟢 Supporters

• •Docker Agent draws heavy interest. The HN thread has 306 points and 144 comments [1]. The project pitches agents that "collaborate to solve complex problems — no code required" [1].
• •Builders are working around Docker rather than away from it. One commenter open-sourced Pullboard in response to the thread [1]. That suggests Docker-adjacent agent tooling is an active area.
• •Self-hosters rely on Docker-based platforms. A Dokploy feature request for an optional database editor has 18 comments and 10 reactions. The author says they run Dokploy "actively" on their own servers [3].
• •Docker remains a security-isolation primitive in agent infrastructure. One GitHub PR moves "Docker enclaves" onto a shared host-owned lifecycle while "preserving their isolation and bounded-disclosure guarantees" [5]. A related WIP PR extends diagnostic retention for Docker executors [6].
• •Projects are fixing their Docker onboarding paths. QWED's PR adds a server image target and makes the Compose stack build, since the README and docs tell users to run the API with Docker or Compose [4].
• •Creative experimentation continues. A Show HN language, Doiter, uses Docker containers as pointers and stack frames [9].

🔴 Skeptics

• •Value of "no code required." One HN commenter asks how it can be a selling point "when we all have agents that can almost instantly puke out all the mostly-correct code you could want" [1].
• •Agent-harness sprawl. The same thread says agent harnesses "are turning into JS frameworks from yesteryear" [1].
• •Orchestration may not be the real problem. The Pullboard author argues the harder challenge is agent coherency and drift over long periods [1].
• •Build caching is unreliable. A BuildKit issue reports GitHub Actions cache failing with ERROR CODE: BlobNotFound roughly 6 out of 7 times [2].
• •Windows/WSL breakage. An issue reports nested virtualization silently disabled after the Oct 2026 cumulative update, with WSL swallowing the error (HCS error 0x8007000D). It has 40 comments and 16 reactions [7].
• •Broken defaults. QWED's published image ran the GitHub Action rather than the API server, and deploy/docker-compose.yml could not build [4].
• •Performance, said jokingly. Doiter's hello-world takes about a minute. The author calls that "not too bad" for the industry, and a commenter says "at least it's better than Java" [9].

⚪ Neutral Observers

• •Cloud Hypervisor as an alternative. Another gh-aw-firewall PR builds a scoped GitHub capability handoff for Cloud Hypervisor agent enclaves, with a maximum one-hour lifetime and allowlists [8]. Docker enclaves appear to be one of several isolation backends in that project [5][6][8].
• •Docker is mostly infrastructure here. In these sources it appears as a build, CI or deployment layer, with little new product discussion beyond Docker Agent [1][2][4].
• •Little 2025-specific commentary. The evidence contains no clear retrospective or trend piece on containers in 2025.

Cross-Platform Signals

• •GitHub dominates. It supplies 16 of the 18 items, and most are operational: bugs, CI failures, PRs and feature requests.
• •Hacker News contributes two items. One is the high-engagement Docker Agent thread [1] and the other is the small Doiter Show HN [9].
• •Divergence. HN is about AI-agent hype and its skepticism. GitHub is about reliability, such as cache failures, WSL regressions and broken Compose builds, alongside security isolation.
• •Consensus. Docker is assumed as a given, and complaints target the surrounding tooling rather than containers themselves.

Community Verdict

Docker is treated as entrenched infrastructure, and the strongest energy is around AI-agent tooling and sandboxing. The loudest conversation, Docker Agent, is met with mixed enthusiasm and skepticism about its pitch [1]. Day-to-day GitHub activity shows practical friction: flaky BuildKit caching [2], WSL virtualization regressions [7] and broken images or Compose files [4]. Sentiment is therefore "useful and ubiquitous, but rough at the edges," with little evidence of anyone abandoning containers.

---

Based on Hacker News + GitHub data from the last 30 days, researched with last30days by Matt Van Horn.