Bug 51770 - Provide docker-compose files for UCS docker appliance images
Summary: Provide docker-compose files for UCS docker appliance images
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Docker
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: App Center maintainers
QA Contact: App Center maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-05 00:28 CEST by Arvid Requate
Modified: 2025-02-05 09:28 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
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):
Customer ID:
Max CVSS v3 score:


Attachments
ucs-docker-compose.tar.xz (1.30 KB, application/x-xz)
2020-08-05 00:28 CEST, Arvid Requate
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2020-08-05 00:28:46 CEST
Created attachment 10447 [details]
ucs-docker-compose.tar.xz

It's possible to use docker-compose to build and automatically setup-join UCS systems based on the UCS appliance images hosted on docker hub and a normal UCS profile file. That way, the setup is more familiar to the docker container workflow, because the user doesn't have to do any interactive steps.

If we decide against this docker-compose approach, it may at least demonstrate a more Docker-style way of setup and we may want to change the instructions on docker hub from the interactive web-based setup to a non-interactive profile-based setup.
Comment 1 Jan-Luca Kiok univentionstaff 2025-02-05 09:28:42 CET
This issue has been filed against UCS 4.4.

UCS 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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