How do I set the jwt_secret in OpenCloud???

[RobertBrown3]

I am running Opencloud in a docker container, and whenever I start it I am getting the following failure:

The jwt_secret has not been set properly in your config for opencloud. Make sure your /etc/opencloud config contains the proper values (e.g. by using 'opencloud init --diff' and applying the patch or setting a value manually in the config/corresponding environment variable).

I am happy to set the jwt_secret, but there is nothing in the documentation on how to so so in a docker container!

1. There is no "opencloud" command included with the git download, so I cannot use "opencloud init".
2. Of course, I could exec into the opencloud container to use the opencloud init command -- except that the container exists after generating the error!
3. I imagine that there is an environment variable that I can use to set the jwt_secret once it is generated, but there is no documentation on what that variable is! Not only that, but there is no tool (that I know of) to generate the jwt_secret anyway.

So: (a) how do I generate and set the jwt_secret for a docker installation, and (b) will someone please document how this is done in the setup documentation?

Thanks in advance for any help in this matter.

[micbar]

If you follow the docs, you can see that you need to initialize openCloud. This creates random and secure secrets.

[micbar]

https://docs.opencloud.eu/docs/admin/getting-started/container/docker

[RobertBrown3]

micbar:

Thank you for the link. I was able to get the jwt_secret initialized and got Opencloud running after changing the permissions on various directories in my installation.

I would like to make a few suggestions on your installation:

1. It might be a good idea to include the text in the "Initialize OpenCloud (First-time Setup)" section of your link into the docker-compose page. It would not occur to a person (like me) who wants to use the docker-compose installation to look into the docker page in order to find out how to initialize the jwt_secret. Why not tell us to do the initialization as a step in the docker-coompose installation?
2. You might want to change the user that creates directories and files for the installation to 1000. Currently, the user who attempts to create files and directories (like, for example, opencloud.yml) is 100999. This creates permission problems in running the initialization and the Opencloud server itself. Since everyone seems to say that everything should belong to user 1000, why not make the user who creates everything 1000?
3. Your installation for Traefik and those using Nginx and Certbot are pretty complete, but I am using Nginx Proxy Manager (NPM), which for some reason is not properly with Opencloud. NPM and various other similar proxy managers handle all the certs required and proper forwarding -- yet your documentation does not take them into account when installing Opencloud. I think it would be a good idea to put something in the documentation on how to install Opencloud for such users.

In any event, again, thanks for the link. I am having problems accessing Opencloud through my NPM, but I believe this is a subject for another discussion.

[RobertBrown3]

Actually: no, the init setup is not done automatically (at least, it wasn't on my installation). That is why I needed your link in the first place. This was a first- time installation which failed to start due to the jwt_secret not being set. If the init had been done automatically, I would not have had to do the initialization command.

If it is supposed to be done automatically, then there is a bug in your docker container startup that needs to be fixed...

As for the docker behaving weirdly when the daemon runs rootless: since I am running it rootless I will just have to chalk up the bad user ID to that...

[micbar]

https://github.com/opencloud-eu/opencloud-compose/blob/main/docker-compose.yml#L13-L16

[micbar]

If you run docker as user 1000, you need to set opencloud container UID to 0 to get uid 1000.

[RobertBrown3]

Actually, that is wrong.

Using UID as 0 gets uid 0: root. Using UID as 1000 gets UID as 100999.

It is weird...

[micbar]

I can feel the pain. 🤪