Bug 50071 - Documentation: Reinitialize Docker App
Documentation: Reinitialize Docker App
Status: CLOSED FIXED
Product: UCS extended documentation
Classification: Unclassified
Component: App Provider
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Nico Gulden
Dirk Wiesenthal
:
Depends on: 50057
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-28 09:40 CEST by Jannik Ahlers
Modified: 2022-07-04 17:23 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jannik Ahlers univentionstaff 2019-08-28 09:40:29 CEST
The changes made for Bug #50057 need to be addressed in the App Provider Documentation:
- new command "univention-app reinitialize $myapp"
- this command can be used in the configure-host script

+++ This bug was initially created as a clone of Bug #50057 +++

We want to be able to reinitialize a running Docker App: This creates a new container but with the latest App Settings.

This is necessary, if the App cannot apply App Settings during runtime but relies on getting those as environment variables during the container creation.
Comment 1 Nico Gulden univentionstaff 2019-10-11 16:55:15 CEST
Added a section about reinitialize to the "React on app settings" section and also described the limitations.

See https://git.knut.univention.de/univention/ucs/compare/4.4-2...ngulden%2F50071-reinitialize-docker-app

For QA, please build branch `ngulden/50071-reinitialize-docker-app` in Jenkins at http://jenkins.knut.univention.de:8080/job/BuildDocBookBranch/

After successful QA, please reopen so I can merge it. Thank you.
Comment 2 Nico Gulden univentionstaff 2019-11-05 14:55:47 CET
The changes are not published yet. Why is this bug closed?
Comment 3 Dirk Wiesenthal univentionstaff 2019-11-06 17:32:08 CET
Okay, reinitialize is mentioned. I am missing one sentence about what it means to "reinitialize" in contrast to, well, not reinitialize:

The container(s) is/are stopped, removed the rebuilt with the new set of App Settings. This may be necessary if the software reads configuration options only once during the startup. Docker does not allow to reset environment variables in already created containers, so one may need to recreate them entirely, otherwise a restart of the container may reset the old behaviour.
Comment 4 Dirk Wiesenthal univentionstaff 2019-11-06 17:36:18 CET
Also, please rephrase:

After the settings are changed, two scripts are executed each with the parameter                <userinput>settings</userinput> parameter.
Comment 5 Nico Gulden univentionstaff 2019-11-19 17:27:13 CET
Rebased the branch and updated the text according to the feedback.