Comment 1 Arvid Requate 2015-10-08 12:58:08 CEST

The Docker App /etc/init.d/<app> scripts only (re-)start containers which have been previously instanciated by the App Center from a Docker image via "docker create". The command to be started ("run") in the container, is defined during the "create" and cannot be changed later. This is a limitation of Docker currently. Experiments with changing the containers config.json have not resulted in usable results, apparently the daemon caches the container definitions. So the original idea of this bug cannot be implemented currently.

The parameters passed by the App Center to "docker create" are derived from the App ini file. This comprises environment variables passed to the container (-v) as well as the command to be run (and its arguments). As discussed with Dirk, it would be possible to first write the settings defined in the App ini file into UCR and then read them from there for the "docker exec". That way, a *user* could ucr set --force a different command. Currently we don't see a use case for this.

If ISVs want to have the possibility to UCR-define the parameters passed during the start of their application, they have the opportunity to do this *inside* the container in their own traditional App specific init.d script. The App Center supports this via the App specific UCR "template" ini file (what's the official wording for this?), where the ISV even can trigger the App Center to allow the Administrator to change the UCR variable at the time of App installation (by specifying "advanced=0").

Setting to wontfix, please get back to me in case you feel that we can and need to do better here.

Comment 2 Stefan Gohmann 2015-10-27 07:48:03 CET

OK, I'm fine with it.

Comment 3 Stefan Gohmann 2015-11-17 12:11:57 CET

UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".