-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plantuml/graphviz crashes on some diagrams on alpine linux arm 64 #2
Comments
Note - if testing is required you can install Termux (https://github.com/termux/termux-app) on Android and install alpine with this helper (https://github.com/Hax4us/TermuxAlpine) and run the script above to replicate on any Android 10/11 device. Raspberry Pi on alpine is the same. Not sure about ARM Mac OSs |
does dot iself work, like described e.g. here: |
so it appears to be a problem with dot / graphviz installation via. However, in my example I did not install dot with a package manager so this problem may be unrelated (https://stackoverflow.com/questions/69377104/unable-to-execute-dot-command-after-installation-of-graphviz-there-is-no-layou). I expected that since the JAR contains graphviz that package manager bugs are not relevant. I will post back when I get dot working |
after downloading the graphviz release and building from source, it works. is there anything we can do to make the packaged graphviz work without this additional step? |
graphviz is not packaged with plantuml, but an optional dependency of the operating system package. e.g. here, arch linux: in alpine i cannot see that the package sets this dependency: you want to report it there, and close the issue here? |
I understand that this is not an issue of Plantuml but since it is a related and recurring issue to Plantuml usage in Alpine Linux, I would like to continue the conversation by asking the following. |
could you try with this released image ? |
Thank you for your answer.
Perhaps not all dependencies are strictly required. However, by looking the Dockerfile in |
Any ideas what the root cause is? Here is my script to replicate:
Output attached.
output.log.txt
The text was updated successfully, but these errors were encountered: