Rockon with multiple containers requires same env variables for all containers

[freaktechnik]

Define a rockon with multiple containers. The two containers require a different set of environment variables to be set by the user. Installing the rockon will fail, due to an env variable that was set in the wizard not existing for one of the containers.

[FroggyFlox]

Hi @freaktechnik ,

Thanks a lot for your interest in multi-containers rock-ons; it's nice to see there's a lot of interest in this.

Unfortunately, I believe you are highlighting an issue that was previously raised (#1588 (comment)) and for which a pull-request was submitted (#1688). I personally am very motivated in getting to that one as soon as things settle down on the relaunch, so it's very encouraging to see that this interest is shared by other users. We have now seen multiple users that would have benefited from this being fixed/enabled, so I will definitely get on that once I can.

Sorry for not being able to provide you with a solution right away, unfortunately.

Hope this helps anyway...

[freaktechnik]

I have found a workaround, which is to have the same set of env vars for all containers. Curiously this repeats the fields in the env var input, but will only show them once in the end table. Of course this only works if there are no env var clashes.

[freaktechnik]

This is what the resulting definition looks like btw: https://github.com/freaktechnik/rockons/blob/master/matrix-synapse.json

In theory only matrix-synapse needs GID and UID and only the postgres container needs the pw (though the pw bootstrapping doesn't seem to have worked in the first place)

[FroggyFlox]

That's a great candidate for a rock-on, especially given its reputation as being a little complex to setup!
Let's hope we'll be able to fix that underlying limitation relatively soon.

Thanks!

[freaktechnik]

Yeah, I've noted some of the caveats with the rockon I ended up with in the README. Essentially the TURN server can't STUN, and I didn't manage to get Element as part of the setup. I've now simply used the Element app for Nextcloud to self-host Element (that plus having set up the database and synapse config manually, which I actually wanted to do since I migrated my synapse). I guess an even more advanced package would also include jitsi, though I think that could be a separate rockon that you can just integrate at rockon setup time. Either way, seeing a more streamlined version would definitively be great!

[freaktechnik]

This also appears to apply to devices.

[phillxnet]

Closing as:
Duplicate of #1588

"Rockons: Invalid environment variabled" #1588

As per @FroggyFlox comment #2202 (comment)