hilbert / hilbert-docker-images

Application with a dynamic choice of docker containers to run
Apache License 2.0
22 stars 8 forks source link

Compile list of container roles #6

Open porst17 opened 9 years ago

porst17 commented 9 years ago

Which containers do we need in addition to the app containers? The list compiled here should be role based and include the main individual components for each such container.

porst17 commented 9 years ago
malex984 commented 9 years ago

Do you mean to add descriptions to each image/directory ?

porst17 commented 9 years ago

It looks like we will have certain containers for providing infrastructure. X11 is currently one. Maybe we will also separate the close button and the menu into individual containers. I would like to keep as much out of the app containers as possible. I created the issue to discuss which separation makes sense.

malex984 commented 6 years ago

currently we only requite hilbert/omd_agent for monitoring system and UI Dashboard.

We rely on the following native services: pulseaudio (custom global setup) and X11 (specially started via nodm). Moreover all the required HW drivers should be installed via puppet.

ps: for development/testing purpose we currently also run hilbert/x11vnc

ps2: we make use of NO Window-Manager (e.g. no openbox or similar is used)

ps3: compositor (compton) will be run from within application containers where transparency is required.

ps4: Close button is not supposed to be used anywhere...