extension-template icon indicating copy to clipboard operation
extension-template copied to clipboard

Docker image to build/test extensions?

Open adsharma opened this issue 1 year ago • 2 comments

I noticed that this template checks out a copy of the duckdb source as a submodule, builds it along with the extension to execute tests etc. While there may be legit reasons because of which things are set up this way, I'm curious to see if anyone has a docker image with a pre-built duckdb that allows me to mount my extension as a volume to build and test.

Benefits:

  • Hopefully faster build times. Even with ninja/ccache, I was running into OOMs and long build times on a 8C/16T laptop with 8GB
  • Unexplained recompilation - repeating make after a successful build should do nothing. But I found it rebuild a small number of things for reasons that are not clear. Culprits: jemalloc, relinking a few things.
  • Faster edit/compile/debug flows for extension developers

The closest thing I could find is this community docker. It can build a ruby extension, but not a C++ extension.

Not a bug. But more of a feature request or a discussion topic.

adsharma avatar Dec 19 '24 18:12 adsharma

This would be cool to have, and pieces are mostly there since CI already builds extensions in a docker environment, it's a matter of putting them together / iterate.

If someone wants to pick this up, contributions are very welcome.

carlopi avatar Dec 20 '24 08:12 carlopi

Looks like this is the CI workflow to be dockerized.

adsharma avatar Dec 20 '24 17:12 adsharma