The solution is to delete the data files which were created during setup by the "127.0.0.1 server process".
I would love to see a possibility to make the "detault-server-setup" optional ( e.g. by setting an environment variable before running the package install ).
I've had similar issues with the rpm postinstall steps. I ended up building my own rpm w/o a postinstall step so that installing the RPM is independent from running and managing a database cluster.
Hi,
some guys ( including myself ) wrote Dockerfiles for FoundationDB:
https://forums.foundationdb.org/t/simple-dockerfile/280/5 https://forums.foundationdb.org/t/how-are-contributing-workers-computed/360 https://forums.foundationdb.org/t/foundationdb-kubernetes-having-issues/383/4
The solution is to delete the data files which were created during setup by the "127.0.0.1 server process".
I would love to see a possibility to make the "detault-server-setup" optional ( e.g. by setting an environment variable before running the package install ).
What are your thoughts ?