Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
dockerfiler vs pkgcache
A side-by-side editorial comparison of dockerfiler and pkgcache — release velocity, themes, recent moves, and the top alternatives to consider.
dockerfiler vs pkgcache: at a glance
What is dockerfiler?
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
After two years of small parameter additions, ThinkR shipped a 1.0.0 that changes the tool's output for every existing user. The vendored copy of renv is gone, generated images default to multi-arch rocker/r-ver running as a non-root rstudio user, and packages come from Posit Public Package Manager binaries instead of a source CRAN mirror.
What is pkgcache?
The metadata cache under pak now speaks to authenticated and corporate repositories.
pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.
dockerfiler vs pkgcache: editorial side-by-side
dockerfiler
0.0INFRA · APIS
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
◆ Current state
After two years of small parameter additions, ThinkR shipped a 1.0.0 that changes the tool's output for every existing user. The vendored copy of renv is gone, generated images default to multi-arch rocker/r-ver running as a non-root rstudio user, and packages come from Posit Public Package Manager binaries instead of a source CRAN mirror.
◆ Where it's heading
The package is being hardened rather than extended. Every user-supplied value that reaches a Dockerfile shell context is validated at function entry, and two long-standing code-injection paths — a crafted renv.lock version string and DCF continuation lines in DESCRIPTION fields — were closed after an internal audit. The new parameters point at production image builds: github_pat via BuildKit secret mounts, strict_install turning install warnings into build failures, and a configurable renv cache path.
◆ Prediction
With the injection surface closed and the defaults flipped, the next releases are more likely to be compatibility work against renv and pak than new generators.
pkgcache
0.0INFRA · APIS
The metadata cache under pak now speaks to authenticated and corporate repositories.
◆ Current state
pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.
◆ Where it's heading
The work has shifted from CRAN-shaped assumptions toward the mixed reality of how R packages are actually distributed now — PPM snapshots, R Universe, private and authenticated registries, Bioconductor, and per-platform binaries across several R versions. Resilience is a recurring theme too: 2.2.5 makes an unreachable Bioconductor a non-fatal condition rather than a failure. MRAN's retirement, handled in 2.2.0 by resolving its prefix to PPM, is a reminder of how much of this package's job is absorbing other people's infrastructure changes.
◆ Prediction
Expect continued tracking of R-devel metadata format changes and new binary platforms as R 4.6 lands, since both already appear in 2.2.5. Further work on authenticated repository handling is the plausible follow-on, given how recently that capability arrived.
Alternatives to dockerfiler and pkgcache
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either dockerfiler or pkgcache.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all dockerfiler alternatives → · See all pkgcache alternatives →
Recent activity from dockerfiler and pkgcache
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agodockerfilerMulti-arch, non-root defaults and a closed injection surface ⚡
- 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
- 1y agopkgcacherepo_auth() brings authenticated repositories to the cache ⚡
- 1y agopkgcacheStops using source URLs for archived PPM packages
- 2y agodockerfilerSystem-requirement detection moves to pak::pkg_sysreqs()
- 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
- 2y agopkgcacheImproves R to Bioconductor version matching
- 2y agodockerfilerDockerfile generation from renv.lock, and parsing back
- 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added
- 3y agodockerfilerGraceful failure without network access
Frequently asked questions
What is the difference between dockerfiler and pkgcache?
They serve adjacent needs but don't currently overlap on shipped themes. dockerfiler and pkgcache are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is dockerfiler better than pkgcache?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dockerfiler and pkgcache are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to dockerfiler?
Top dockerfiler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dockerfiler alternatives" section above for the current picks, or visit /alternatives/dockerfiler for the full list with editorial commentary on each.
What are the best alternatives to pkgcache?
Top pkgcache alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgcache alternatives" section above for the current picks, or visit /alternatives/pkgcache for the full list with editorial commentary on each.