i don't know what can be the problem, as mentioned, the full docker image work for us, we are using it with docker for windows/macos and also running it on linux directly, so it is working fine.
if this issue only happens when you are building your own image, then something must be wrong there, but we can not know without testing a complete docker image.
Each image generated by docxImage generates a bookmark that points to the new image, customizing the bookmark (with bookmarkName option) will allow for other images to be able to create hyperlinks that target this specific image (just make sure to make the hyperlink of an image dynamic too with handlebars, the requirement is that the target resolves to #bookmarkName). using these two features, the custom bookmark name and the dynamic hyperlink target will allow to achieve dynamic linking between images in the document.
The error-prone process would be to start your local v2 instance and import there compatible export. Then update the local v2 instance to v3 and let it process changes during the start. Check everything works properly and then make the final export you need.
Hello, thank you for your reply. We identified that the issue was caused by the developer's Chrome browser auto-saving the password settings. Accessing the studio in Safari resolved the issue. Nonetheless, this remains an interesting research topic for future reference.
