Bug 43522 - Container should execute defined scripts instead of hard coded default scripts
Container should execute defined scripts instead of hard coded default scripts
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on: 43521
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-09 22:35 CET by Dirk Wiesenthal
Modified: 2019-01-03 07:19 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?: Yes
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 Dirk Wiesenthal univentionstaff 2017-02-09 22:35:17 CET
/usr/share/univention-docker-container-mode/setup calls /usr/share/univention-docker-container-mode/update_app_version to actually install the App.

If one or two more scripts are to be placed into the file system "manually" by the integration scripts, one would do this in a custom
  /usr/share/univention-docker-container-mode/update_app_version_custom

But this script is not called when initially setting up the container - any additional command put into update_app_version_custom has to be copied to setup_custom. We should call
  $(univention-app get "$APP_ARG" DockerScriptUpdateAppVersion)

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

If an App ships its own setup script, it is copied into the container just before execution. This may be too late especially for scripts like update_app_version or update_packages.

These scripts are called by setup. But only the custom setup script is copied in this case, the custom update_app_version script is not. There is no way to execute this very script during setup.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:19:37 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.