use pandoc containers as a base instead of building pandoc ourselves #233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 3.5 (October 2024) pandoc/core containers have been available in both amd64 and arm64 flavors. Lack of arm64 support has been a reason to build pandoc ourselves up to now. However, Haskell takes a very long time to compile so this is expensives in terms of CI and release.
This PR updates the Docker build to use pandoc/core as the "RUNBASE" (while building TeX Live and other tools from Debian bookworm as before)
A future PR might experiment with dropping the TeX Live build as well, but our TeX dependencies are pretty substantial so I'm not sure what that will get us.