Images
The available inndx container image variants and when to use each.
This page lists the container image variants inndx publishes and explains when each is needed. Use it as a quick reference when wiring up a deployment or evaluation.
Image variants
inndx publishes two variants of its container image at each released version, distinguished by the image tag.
The base image, tagged inndx-image:<tag> (for example inndx-image:0.3.0), contains the inndx binary and everything needed to run any service. Every deployment mode and every service runs from this image.
The browser image, tagged with a -browsers suffix (for example inndx-image:0.3.0-browsers), is the base image plus a bundled browser runtime. It includes Playwright and the Chrome DevTools Protocol runtime, with Chrome and Chrome for Testing.
Choosing an image
Use the base image for everything unless a crawl uses a browser-based fetch client that renders pages inside the fetcher.
The browser image is required for the fetcher when a crawl uses the playwright or cdp client, because those clients run a browser in the fetcher process. The remote_cdp client connects to a browser running elsewhere, so the fetcher driving it does not need the browser image. All other services (orchestrator, parser, sink, analytics) never need the browser image.
The browser image is considerably larger than the base image because of the bundled browser, so use it only where it is needed. For the fetch clients themselves, see Clients and the guide Fetch with a browser.