History

Alec Grieser 7b12374a87 Fixes #1690 : Server docker image hard-codes 4500 in a few places This makes the default public port for starting FDB processes the same as the FDB_PORT. This is probably necessary given #1714, especially for coordinators, though it might not be necessary for other processes in the cluster. This can almost be used to start up multiple FDB processes locally and then access them from the same machine, but that (unfortunately) requires both the other processes in the docker compose network and the host machine to agree on what IP to use for the coordinator. But as that machine has different IPs in those networks, they cannot be made to agree.		2019-06-18 18:36:12 -07:00
..
README.md	Fixes #1690 : Server docker image hard-codes 4500 in a few places	2019-06-18 18:36:12 -07:00
docker-compose.yml	Fixes #1690 : Server docker image hard-codes 4500 in a few places	2019-06-18 18:36:12 -07:00
start.bash	Fixes #1690 : Server docker image hard-codes 4500 in a few places	2019-06-18 18:36:12 -07:00
stop.bash	Fixes #1690 : Server docker image hard-codes 4500 in a few places	2019-06-18 18:36:12 -07:00

README.md

Local Docker-based FoundationDB Cluster

This contains a sample docker-compose.yaml and some simple startup and teardown scripts for running a simple single-instance FoundationDB using the Docker image specified in this repository. This uses the host networking option to expose the server process to its host machine.

This depends on having the FoundationDB client installed on your host machine to work properly. This can be done using one of the client packages available on our Download page. The startup scripts included here depend on fdbcli from one of those packages, and any client that wishes to connect will need a copy of the FoundationDB native client in addition to its binding of choice. Both the CLI and the native client are installed in all of our client packages

Once those dependencies are installed, one can build the FoundationDB Docker image:

docker build --build-arg FDB_VERSION=6.1.8 -t foundationdb:6.1.8 ../..

Then one can start the cluster by running:

./start.bash

This starts up a single instance FoundationDB cluster using the docker-compose.yaml and configures it as a new database. This will write the cluster file information to docker.cluster. One should then be able to access the cluster through the CLI or one of the bindings by using this cluster file. For example:

fdbcli --exec status -C docker.cluster

To stop the cluster, one can run:

./stop.bash

Note that all data are lost between reboots of the processes as they have not been configured to use a persistent volume (but write to Docker's temporary file system).