Fully in-browser container builds
A new web application allows users to build container images directly in their browser using client-side code. This research prototype enables users to select base images, run shell scripts, and export images as tar files. While the concept may seem gimmicky, it highlights the potential of custom container tooling and the benefits of developing personalized solutions.
- ▪The application allows users to build containers entirely in the browser.
- ▪Users can pick a base image and specify a shell script to run upon startup.
- ▪The source code for the builder is available for those interested in the details.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Adolfo Ochagavía |
| Canonical URL | https://ochagavia.nl/blog/fully-in-browser-container-builds/ |
| Publication time | Mon, 25 May 2026 06:19:36 -0500 |
| Retrieval time | 2026-05-25T11:37:36.700Z |
| Last seen | 2026-05-25T11:37:36.700Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fJDBgg_8iZ1D |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Fully in-browser container builds 24 May, 2026 Containers are fun. The ecosystem is incredibly open, with the internals right there for anyone to explore. Once you wrap your head around the specifications, you unlock the power to build custom tools and may even discover unexpected use cases1. Speaking of “unexpected use cases”, today I have a demo to share: a web application that builds containers right in your browser, relying only on client-side code. Try it out Seeing is believing, so why don’t you head to the demo and build a container? You will be able to: Pick a base image Specify a shell script to run upon container startup Export the resulting image as a tar file, which you can then load into docker Important: this is a research prototype, don’t use it for anything serious.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Adolfo Ochagavía.
Discussion
0 commentsMore from Adolfo Ochagavía
