Creating master encryption key fails

Hello,

I’m starting cells from docker with a basic docker-compose file (the one currently on https://hub.docker.com/r/pydio/cells/ ) and everything is working except creating a master key. The error I receive for this is:

{"id":"data-key","code":500,"detail":"failed to get password. Make sure you have the system keyring installed%!(EXTRA *errors.errorString=failed to read from keyring. Make sure you have the system keyring installed)","status":"Internal Server Error"}

In the logs themselves:

cells_1  | 2018-10-22T18:50:03.229Z	ERROR	Failed to the master key	{"error": "exec: \"dbus-launch\": executable file not found in $PATH"}
cells_1  | 2018-10-22T18:50:03.229Z	ERROR	failed to save master key	{"error": "exec: \"dbus-launch\": executable file not found in $PATH"}
cells_1  | 2018-10-22T18:50:03.229Z	ERROR	pydio.rest.config	Rest Error 500	{"error": "{\"id\":\"data-key\",\"code\":500,\"detail\":\"failed to get password. Make sure you have the system keyring installed%!(EXTRA *errors.errorString=failed to read from keyring. Make sure you have the system keyring installed)\",\"status\":\"Internal Server Error\"}"}

Am I right in assuming this problem is almost certainly going to go away if I run cells under systemd instead of pulling it in via docker?

Hi,
this issue happens because the container did not have a keyring system installed, we will publish a new container with the keyring pre-installed.
If you still want to use the current container, you can install it inside the container.

1 Like

@zayn Could you please let us know how to install the keyring in the container? The container seems to be based on busybox and there doesn’t seem to be a package manager installed

Hi,
i looked at it and i believe that the keyring inside a container is tricky,
you could make it work but it will need some manipulations on your end
(the issue is that containers start with root user, and to unlock the keyring you need the password, so unless you create a user with a password and start cells with the same user inside the container).

here are the requirements.

packages : dbus-user-session  && gnome-keyring


dbus-run-session

gnome-keyring-daemon —unlock (can be launched in foreground with —foreground)
<input user password>
<ctrl+d>

We are going to work on a better solution that will abstract this.