docs: document slim Docker images and package manager setup - #4082
docs: document slim Docker images and package manager setup#4082vladfrangu wants to merge 9 commits into
Conversation
89bb6a1 to
00eb385
Compare
github-actions
Bot
added
the
t-tooling
barjin
left a comment
barjin
left a comment
There was a problem hiding this comment.
lgtm, just one (mostly unactionable) note from my quick check ⬇️
|
|
||
| ### Slim variants | ||
|
|
||
| Every Node.js image is also published as a slim variant, with a `-slim` suffix appended to the tag (e.g. `24-slim`, `24-1.60.0-slim`, `24-beta-slim`). Slim images do not preinstall `apify`, `crawlee` or `typescript`. They only ship the browser automation library the image is built around (for example `puppeteer`, `playwright`, or `camoufox-js` with `impit`), and `apify/actor-node:24-slim` ships no npm packages at all. This makes them smaller and faster to pull, and your project's `package.json` is the single source of truth for dependency versions. |
There was a problem hiding this comment.
It's probably obvious, but it took me a second read-through to realize the -slim images contain the library (e.g., Playwright) and the matching browser binaries.
There was a problem hiding this comment.
Damn... do I need to multiline it? :D
There was a problem hiding this comment.
No need, it's rather obvious, it just didn't click immediately for me 😅 the PR is gtg by me 👍
|
IMO we should have this documented here, somehow. The canonical place might be in the apify docs, but some mention in crawlee docs on how to use crawlee in a docker surely makes sense to me. There is very little in the images that is actually apify specific, right? If there are native alternatives to our images that works fine with crawlee, I wouldnt mind documenting those in here and only linking to apify docs, but some docs around this topic should stay as part of crawlee.dev |
B4nan
left a comment
B4nan
left a comment
There was a problem hiding this comment.
this should be ported to latest stable snapshot too, its not related to v4 anyhow
also we need to resolve the increase in size which the corepack PR did (apify/apify-actor-docker#303 (comment)), maybe it wasnt a good idea to bake corepack in? i know pnpm folks no longer suggest its usage, and yarn v6 will also provide a native way to install different versions instead of suggesting corepack.
5 participants
Updates the Running in Docker guide to match the current
apify/apify-actor-dockerimages:-slimtag variants (no preinstalledapify/crawlee/typescript, only the automation library the image is built around) and recommend them by default.packageManagersupport, flatnode_moduleslinker config, and the shared/pkg-cachelocation, plus how to override the linker viaENVsince env vars take precedence over.npmrc/.yarnrc.yml.:24.[🤖] Claude Code using Fable 5