We probably don’t need fancy Docker here. Eunit and dev/run already setup fdbserver automatically if the binary is found. A two stage build that copies fdbserver into the existing image is probably all that needs to happen.
I’m limited to typing one handed for the forseeable future so I won’t get to it myself. But i’m more than happy to chat on email or irc if someone has questions. Here’s build notes for macOS: https://gist.github.com/davisp/aa6f526b8fd0441f2035c93774828798 On Tue, Feb 18, 2020 at 5:08 PM Joan Touzet <woh...@apache.org> wrote: > Thanks Alex! > > The Jenkins setup currently runs each CI job in a container per host, > and Docker-in-Docker can be a bit challenging. Hopefully the alternative > "expose your parent Docker socket inside of Docker with -v" approach, as > described at > https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ > will be sufficient. We'd also need the docker cli inside the CI image, > which shouldn't be too hard to add. > > For builds on master itself (post-merge, to check a wider set of > platforms), we currently have FreeBSD builds where there is no Docker. > We'll need to sort out a solution for that as well. I can preinstall FDB > on those hosts but the Jenkinsfile will have to take care of starting > and stopping FDB as pre/post actions. > > -Joan > > On 2020-02-18 17:22, Alex Miller wrote: > > And for whoever does pick it up, there's some examples of docker-ify-ing > FDB and running it via docker-compose in apple/foundationdb's > packaging/docker/< > https://github.com/apple/foundationdb/tree/master/packaging/docker> , > and the Dockerfile therein is built and pushed as foundationdb/foundationdb< > https://hub.docker.com/r/foundationdb/foundationdb/tags> on docker hub. >
