Closed JJ-Author closed 5 years ago
I have not been able to reproduce this build issue locally, nor on Docker Hub. I'm willing to bet that you won't be able to reproduce this issue anymore either.
You attempted to build when rocksdb's master branch was in an unlucky state. See this commit that fixed the issue: https://github.com/facebook/rocksdb/commit/5265c5709eb19f49c047345b0046d8c5f09600ad
We can leave this issue open for now, because it might happen again. It could possibly be prevented in the future by explicitly installing rocksdb's latest release. There are several ways of doing this and I need to pick one.
OK. I confirm it works again. I think we can close the issue. So far no need to deal with bad commits on a master branch. However, I don't know how fast python-rocksdb is updated so maybe it makes sense to checkout the latest release tag for rocksdb only to make it more stable?
I thought it would be nice to get rid of git altogether. GitHub's GraphQL API looks pretty neat:
https://developer.github.com/v4/explorer/
{
repository(owner: "facebook", name: "rocksdb") {
releases(last: 1) {
nodes {
name,
tagName,
url
}
}
}
}
Unfortunately, it requires authentication and that's annoying in a Dockerfile. I'm now testing an alternative download method, based on an available 302 redirect.
I created a generalized script for downloading the latest release from a GitHub repo. It might interest you for your own Docker endeavors, if you want to stay away from git, that is.
Provided as a gist (well, sort of): https://github.com/stamkracht/gists/blob/master/github/download_latest_release.py