Bug 50767 - prevent to create docker networks when they are already in use
prevent to create docker networks when they are already in use
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-02-01 15:14 CET by Dirk Ahrnke
Modified: 2020-03-09 11:22 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.023
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Ahrnke univentionstaff 2020-02-01 15:14:31 CET
https://help.univention.com/t/adding-ethercalc-as-application-add-some-wrong-route-to-my-ucs-server/14200 describes a problem where a user installed a docker-based app and some of the internal network services did not work anymore afterwards.
The only thing that we tell the users when they install such an app is, that it is based on Docker and I guess that some users may not be aware that their network setup will be changed.

It might be worth to think a about a check which prevents the creation of the docker networks when they are already in use in the current environment.

another option: 
add additional text to the warning when installing the first docker app, mentioning the creation of the network