Bug 39870 - Produce "official" Docker appliance images
Produce "official" Docker appliance images
Product: UCS
Classification: Unclassified
Component: Docker
UCS 4.1
Other Linux
: P5 enhancement (vote)
: UCS 4.1-x
Assigned To: App Center maintainers
Depends on: 39187
  Show dependency treegraph
Reported: 2015-11-11 09:02 CET by Arvid Requate
Modified: 2019-01-03 07:22 CET (History)
4 users (show)

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):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2015-11-11 09:02:18 CET
Docker offers a build service which pulls a Dockerfile from github. If it follows certain guidelines the image is supposed to be advertised as "official" on hub.docker.com. This might be a good way to advertise UCS as an appliance and we should aim at getting the images currently available on https://hub.docker.com/u/univention/ into that status.

The Dockerfile and scripts used to build the ucs-stem-amd64 image are already committed into ucs-4.1/internal/univention-docker-dev. They should be commited to github in a way that is accepted for official Docker image builds.

Additionally the scripts for building ucs-generic-amd64:4.1-0 and ucs-master-amd64:4.1-0 and the other role images should be integrated into a Dockerfile following the example of ucs-stem-amd64 and uploaded.

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

We should create UCS 4.1 docker images and upload them to the docker hub.
Comment 1 chymian 2016-10-18 14:32:56 CEST
is there a chance to please get the dockerfiles and possible installation scripts to reproduce, how a container-installation works?
I aim to install UCS in an LXC-Container, which does not work starting with an wheezy container.

any prerequisites?

Comment 3 Arvid Requate univentionstaff 2016-10-20 21:43:43 CEST
Sorry, the link I posted is not usable, I'll think about a way to make the scripts and Dockerfiles available.
Comment 4 Christian Wantia 2016-11-22 13:20:00 CET
Same requirement here. I would like to run UCS in an LXC container too.

Are there any dockerfiles, howtos, guides, checklists or notes, that would help someone, who is experienced in debian/ubuntu server administration?
Comment 5 Arvid Requate univentionstaff 2016-11-22 14:52:03 CET
We have a Debian source package containing the scripts and Dockerfile templates.
On a UCS 4.1-4 system this can be installed simply by running the following two commands:

ucr set repository/online/unmaintained='yes'
univention-install univention-docker-dev

You can also directly download the package from




With the files installed to /usr/share/univention-docker-dev:

1. A debootstrapped UCS "minbase" image can be created with:

/usr/share/univention-docker-dev(scripts/create-minbase-image.sh \

2. Building on that, a "stem" image can be created, containing files common to all UCS server roles:

/usr/share/univention-docker-dev/scripts/create-docker-ucs-stem-image.sh \

3. Building on that "stem" image, either a "generic" or a specific role image can be created, e.g. a master:

/usr/share/univention-docker-dev/scripts/create-docker-ucs-role-image.sh \
  4.1-3 master

The result should be exactly what https://hub.docker.com/u/univention/ provides.
Comment 7 Christian Wantia 2016-11-22 17:32:01 CET
Thanks. This helps a lot.
Comment 8 Stefan Gohmann univentionstaff 2019-01-03 07:22:57 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.