Bug 40256
| Summary: | App Center not usable if docker is not running | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Alexander Kläser <klaeser> |
| Component: | UMC - App-Center | Assignee: | UMC maintainers <umc-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | gohmann |
| Version: | UCS 4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| What kind of report is it?: | --- | 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): | Error handling, Usability | |
| Max CVSS v3 score: | |||
BTW, the docker service cannot be controlled via the UMC services module. |
When docker is disabled, I receive the following error when launching the App Center: > The command has failed: The docker service is not running! The App Center will > not work properly. Make sure docker.io is installed, try starting the service > with "service docker start" IMHO, this should only be a warning, as there are (and will be) scenarios where one would not like to have docker running. One example could be that the range 172.16/12 (used by docker) collides with an internal real network (e.g., Ticket#2015121021000187). Thus the App Center should still work when docker is not available.