Vulkan and ANGLE Initialization Errors in Docker
IronPDF logs a Vulkan or ANGLE initialization error in Docker containers, AWS Lambda, Azure App Service, Google Cloud Run, and CI/CD pipelines.
ERR: Display.cpp:1021 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons...
IronPDF's embedded Chrome Embedded Framework (CEF) attempts GPU rendering via Vulkan when no explicit GPU mode is configured. Docker containers running without GPU access or display drivers cannot initialize Vulkan, triggering this error. Despite the log message, IronPDF continues rendering and produces valid PDF output. The error is non-blocking.
Solution
Disable GPU rendering and enable single-process mode to prevent the GPU initialization attempt and suppress the error:
IronPdf.Installation.ChromeGpuMode = IronPdf.Engines.Chrome.ChromeGpuModes.Disabled;
IronPdf.Installation.ChromeBrowserEngineSettings.SingleProcess = true;
IronPdf.Installation.ChromeGpuMode = IronPdf.Engines.Chrome.ChromeGpuModes.Disabled;
IronPdf.Installation.ChromeBrowserEngineSettings.SingleProcess = true;
Imports IronPdf
IronPdf.Installation.ChromeGpuMode = IronPdf.Engines.Chrome.ChromeGpuModes.Disabled
IronPdf.Installation.ChromeBrowserEngineSettings.SingleProcess = True
Set these properties before the first call to ChromePdfRenderer. This configuration is recommended for all Docker deployments where GPU access is unavailable.
For the full Docker setup reference, see the IronPDF Docker guide.

