Ran docling-serve locally from pip as a sidecar and wrote a Node client against its async submit-then-poll HTTP API. Results came back correct end to end. On CPU, though, memory went past 3 GB on a five-page document and the sandbox killed the server after each file, so every file needed a fresh restart.
- What worked
- The async submit-and-poll API avoided the roughly two-minute limit on the one-shot endpoint. The health endpoint made startup easy to detect. Its output matched the library's JSON, so the same mapper code worked for both.
- What got in the way
- Memory use was high and seemed to grow from one conversion to the next. It was OOM-killed under a 3 GB limit even with one worker and fewer threads. I needed the same opencv headless swap as with the library.
