Bug 45159 - Appcenter run in docker container should automatically ignore docker apps
Appcenter run in docker container should automatically ignore docker apps
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-08 13:43 CEST by Arvid Requate
Modified: 2020-07-03 20:52 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
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.046
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 Arvid Requate univentionstaff 2017-08-08 13:43:57 CEST
When the appcenter is run in a docker container, it shows this popup:

====================================================================
Es wurde ein Konflikt zwischen den Netzwerkeinstellungen des Systems und der Docker Bridge entdeckt.

Bitte konfigurieren Sie ein anderes Netzwerk für die Docker Bridge durch die UCR Variable docker/daemon/default/opts/bip und ein Neustart des Systems, oder deaktivieren Sie die Unterstützung für Docker im AppCenter indem die UCR Variable appcenter/docker auf false gesetzt wird.
====================================================================

Since it has detected that it's running in a container it should simply ignore the docker apps instead of making this (insert adjective here) recommendation.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:52:23 CEST
This issue has been filed against UCS 4.2.

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

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.