Create official Docker image on Docker Hub

[atombender]

As with FoundationDB, there's no official Docker image, despite the presence of a Dockerfile. It'd be nice to have an official image.

[apkar]

I assume you are asking about Docker image for the build. That is what Dockerfile is for. Publishing image for the build can be done quickly. As you can see in the FoundationDB case, Docker image for running is a bit complicated. There is an ongoing PR for this on FoundationDB. Once that is merged we can follow the example.

cc: @AlvinMooreSr

[atombender]

Yes, I'm talking about an official image, not a Dockerfile. The foundationdb repository on Docker.com is where I'd expect to find it.

[apkar]

Ah, sorry I was not clear. We can have two docker images - one for build and one for deployment. We definitely want to do both. Docker image for build will happen soon and image to deploy Document Layer will happen after.

[apkar]

PR on FoundationDB core repo for docker image apple/foundationdb#887

[apkar]

We can follow the example of FoundationDB docker image. There are a couple of details which are not trivial, writing them down here hoping to see better ideas.

• FoundationDB client libraries
  • Get client libraries on startup - If there is a way to find out FDB server version from the client, then we could get the required client library on startup. This will increase the startup time. As far as I know, it is not possible as there is no easy way to get FDB server version.
  • Include client libraries in the image - client libraries will be downloaded during the docker image build process. This would mean we have to update the Document Layer docker image with new FoundationDB releases. I am thinking of going with this approach.
• Cluster file
  • We could make this an environment variable which could be set at runtime. We have to pass the complete cluster file text as an environment variable. Can't think of any better approach so far.

cc: @brownleej

[brownleej]

I think that the ideal way to get the cluster file and the client libraries will vary based on how someone is deploying the image, e.g. through Swarm, Kubernetes, or some other system. In the main FDB docker image, we have a script for generating a cluster file based on looking up coordinator names in DNS, but that probably won't work outside a simple local testing environment.

[platinummonkey]

In the main FDB docker image, we have a script for generating a cluster file based on looking up coordinator names in DNS, but that probably won't work outside a simple local testing environment.

I think this would be great if it was just a static file. Then the user can wrap whatever they want on how to get that in there: volume mount, some ConfigMap mount, or some script to generate this on the fly.

FoundationDB client libraries

I think this will also be language and build-system dependent. maybe just provide a template for a simple stripped down image tagged by version that people could base off of, or use a template to add to their existing images. Honestly I'd worry about this last $0.02.

Though personally I'd vote for starting simple.

[apkar]

Dockerfile is available now.

@AlvinMooreSr can you push the image to Docker Hub, please?

[apkar]

Thanks @AlvinMooreSr!

foundationdb/fdb-document-layer:1.6.0 is available now.

[bencherian]

@apkar @AlvinMooreSr Is there a plan to push the 1.6.1 release to DockerHub as well?

[apkar]

@bencherian Yeah, we are still in the process of releasing. It's going to happen this week.