Docker ENTRYPOINT Drops Runtime Arguments

Updated:July 2, 2026

On IronPDF 2026.3, the Docker image ships with a hardcoded ENTRYPOINT. Arguments you append to docker run are silently ignored and never reach IronPdfEngineConsole, so startup options like browser limits cannot be set without rebuilding the image.

docker run <image> chrome_browser_limit=2

The Dockerfile defines the entry command as a plain string with no argument-forwarding expression:

ENTRYPOINT dotnet IronPdfEngineConsole.dll linux_and_docker_auto_config=true

Because the command omits $@ (or an equivalent shell forwarding form), anything appended to docker run is dropped before it reaches the engine.

Expected

dotnet IronPdfEngineConsole.dll linux_and_docker_auto_config=true chrome_browser_limit=2

Actual

dotnet IronPdfEngineConsole.dll linux_and_docker_auto_config=true

Solution

Upgrade IronPDF to 2026.4 or later. The fix corrects the ENTRYPOINT definition so additional runtime arguments are forwarded to IronPdfEngineConsole, letting you pass options such as chrome_browser_limit through docker run without rebuilding the image.

Curtis Chau

Chat with engineering team now

Technical Writer

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

...

Ready to Get Started?

Nuget Downloads 19,820,650 | Version: 2026.7 just released