We deleted our Dockerfiles: a better, faster way to build container images

RWX describes replacing its application Dockerfile and Docker build CI step with RWX run definitions that package the filesystem outputs of graph-based, cacheable tasks into container-image layers. The company argues this approach improves build speed by distributing independent tasks across right-sized machines, allowing parallel execution, and using content-based caching with file filters so unrelated changes do not invalidate downstream work. Unlike Docker and BuildKit’s sequential layer caching and compressed image transfers, RWX says it automatically resolves cache entries from repository contents, clones source code directly on build machines rather than uploading full build contexts, and stores layers uncompressed to prioritize modern network speeds over compression time. RWX also emphasizes improved observability through retained logs, task diagnostics, and explorable filesystems, and offers GitHub Actions integration for building and pushing images while presenting its platform as a way to create reproducible, portable container artifacts without conventional Dockerfiles.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.