Skip to content
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

Docker image to build/test extensions? #100

Open
adsharma opened this issue Dec 19, 2024 · 2 comments
Open

Docker image to build/test extensions? #100

adsharma opened this issue Dec 19, 2024 · 2 comments

Comments

@adsharma
Copy link

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.

@carlopi
Copy link
Contributor

carlopi commented Dec 20, 2024

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.

@adsharma
Copy link
Author

Looks like this is the CI workflow to be dockerized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants