Closed kylebjordahl closed 4 years ago
I came here for the same problem. While I didn't find a way to set the SuperUser password, here is how I got access to the auto-generated one:
docker logs murmur 2>&1 | grep Password
@DaniDipp has the correct normal solution for this for a new DB startup: obtain the password from the murmur container logs at first run, and then connect using it in the client and change the superuser password from there.
I went ahead and added functionality to support specifying/resetting the superuser password via a new environment variable MURMUR_SUPW as well. Murmur will not fully start or accept connections with -supw in the command line. Use -e MURMUR_SUPW="newpasswordhere"
once and then remove it from the container run command or compose file.
I've tried providing
-supw MyPassword
in theMURMUR_OPTS
environment variable, however the entrypoint script puts the supplied options at the beginning of the argument chain (presumably so that the ones provided in the script take precedence?) but this causes an error from murmur, as it requires that-supw
is the last argument.I'd be glad to create a PR to add an additional environment variable at the end of the chain if that's helpful, but if there's a better way, please let me know.
OS/distribution version: