-
Notifications
You must be signed in to change notification settings - Fork 133
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
Development image with Nouveau #257
Comments
Hi Helio, so you would like to access/use an "official" docker image which uses the current main branch, what we would update from time to time (maybe monthly)? We provide some cochdb-docker dev-versions here and here. I think we need to update this to use nouveau. Would that work for you too? Best, Ronny Link to the SW360-PR: eclipse-sw360/sw360#2392 |
Hi @big-r81 Yep, if we have a dev version with nouveau integrated and published, that would be enough. Thanks for quick answer. |
Hey, as an additional info, we have some artifacts (source, debs and rpms) after every ci run (but no docker image). |
That would be useful for some people using the bare metal approach. Thanks |
Nouveau images will be available shortly once docker-library/official-images#17633 lands
|
Thank you guys. |
Hello all
I'm Helio, one of the maintainers from Eclipse SW360 project.
We've been using CouchDB since the beginning, and now we're planning to get rid Lucene and go after nouveau implementation. The latest interactions always used CouchDB as a docker image instead of bare metal.
On the new main codebase, we already have a PR ready for the entire modification, and I asked to wait for two reasons:
So this is exactly what this issue is about, asking the possibility to create one more image on the pool where marked as a test or devel, whatever decided, and provide it together with main docker, so we know that always came from couchdb team, and not from some third party solution.
If this is feasible, I'm willing to help do the code and create a PR in this repo, otherwise, I'll be ok on maintaining it on our side, just need check out with couchdb team before.
The text was updated successfully, but these errors were encountered: