Univention Bugzilla – Bug 43522
Container should execute defined scripts instead of hard coded default scripts
Last modified: 2019-01-03 07:19:37 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.
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.