mermaid throws error "vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER"

[madmas]

When trying to use the mermaid container image, i get this error message:

mermaid-1 | {"level":"error","time":1711364439841,"pid":1,"hostname":"71631a828926","stderr":"Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER\n at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)\n at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)\n at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)\n at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)\n at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)\n\nWarning: Couldn't load Vulkan. Searched /usr/lib/chromium/libvk_swiftshader.so, /usr/lib/chromium/libvk_swiftshader.so, /usr/lib/chromium/libvk_swiftshader.so, libvk_swiftshader.so.\n at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:299)\n at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:310)\n at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)\n at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)\n\nWarning: Failed to load libEGL.so\n at DiscoverPhysicalDevices (../../third_party/dawn/src/dawn/native/opengl/BackendGL.cpp:61)\n\n","msg":"chrome process"}

It seems to be related to Chrome, maybe an incompatible version is installed in the image?

Any hints how to solve this?

[ggrossetie]

I also get this warning but Mermaid is working fine since Chromium fallback to another engine.

[ggrossetie]

Could you please confirm that despite the error/warning message it works?

[madmas]

@ggrossetie For me, it did not - it stopped processing. I build an workaround by setting um my own image.

[ggrossetie]

Interesting, what did you change? Any additional stacktraces/errors ?

[madmas]

We created an new mermaid image based on pupeteer:latest see https://gist.github.com/madmas/f42300f1056aa9cce1e0485c2077b46e we know it´s a pretty rough workaround :O