When to Use the Dev Image
Use the dev image (checkly/agent:X.Y.Z-dev) when your checks require npm packages with native dependencies that need compilation. Common examples include:
sqlite3- SQLite databasezookeeper- Apache ZooKeeper client
Available Tags
Versioned Tags (Recommended)
Floating Tags
Use versioned tags for reproducible deployments. Floating tags (like
:dev) may change between pulls.What’s Included in the Dev Image
The dev image adds the following to the standard image:| Tool | Purpose |
|---|---|
gcc, g++, make | Compile native extensions |
python3 | Required by node-gyp |
npm install.
How to use it
The dev agent works exactly like the standard agent, but includes the build tools required to compile native modules. To use the dev variant, simply change the image tag:Dev agent (with build tools)
FAQ
Can I use the dev image in production?
Yes, the dev image is production-ready. It contains the same runtime as the standard image, plus build tools. The only tradeoff is a larger image size.Do I need the dev image for Playwright checks?
No. Playwright and its dependencies are pre-installed in both variants. You only need the dev image if your check code imports npm packages with native dependencies.How do I know if a package needs the dev image?
Ifnpm install fails with errors about node-gyp, python, gcc, or “compilation failed”, you likely need the dev image.