Univention Bugzilla – Bug 48100
Document support for docker multi container setup per app in the App Center
Last modified: 2018-12-11 14:50:06 CET
The support for docker multi container setup per app in the App Center should be documented in the App Provider documentation. The setup currently only allows a single YAML file for the docker compose setup. Environment variables and references to pre-filled volumes are not supported currently. The life cycle scripts can only deal with one container. As a workaround, the app provider should additionally provide the location to the main docker image from the yaml file to the docker image setting in the provider portal. The scripts will then refer to this image. Port redirection should still be configured in the portal, as well as the webinterface and port setting.
A new section has been added: http://jenkins.knut.univention.de:8080/view/Doku/job/UCS-4.3/job/UCS-4.3-2/job/HandbookAppProvider/lastSuccessfulBuild/artifact/webroot/app-provider-4.3.html#create-app-with-docker:compose A reference to the UCS errata version needs to be added. Currently, the text says it uses Docker Compose 1.8.0 and supports the compose file format in version 2.0, according to the implementation information. https://docs.docker.com/compose/compose-file/#reference-and-guidelines says that compose file format is supported with Docker Compose version 1.10.0+
Missunderstanding. Removed the hint on Docker Compose version and just kept the information on compose file version 2.0.
Reverted the changes from the 4.3-2 branch.
Created attachment 9762 [details] Doc build with changes For QA, the attached build includes the changes to the documentation.
Needs to be updated to latest final implementation after QA.
Created attachment 9768 [details] New Document build
Updated the documentation after the implemtenation has been verified. See https://git.knut.univention.de/univention/ucs/compare/4.3-2...ngulden%2F48100 for the changes. For QA: The latest build is attached as PDF.
Bugzilla does not allow me to add a new build and mark the others as obsolete. The last build: http://jenkins.knut.univention.de:8080/job/BuildDocBookBranch/lastSuccessfulBuild/artifact/webroot/app-provider-4.3.html I added the errata update number.
Ok, I only made small adjustments. I deleted the part where it was stated that Volumes and Database integration fields may be left empty. This is true, but technically it does not matter. Should they specify volumes, they are added to the main service. Should they specify a database, the database is created and the environment variables are added. All these fields make little sense, but they work, should anyone use them. Technically, "--env-file" file integration is currently not available in multi container apps. I guess we can ignore that until someone really fills in something and wonders why it is nowhere applied.
published