Bug 42084 - use appid as container name
use appid as container name
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-22 16:27 CEST by Felix Botner
Modified: 2018-07-03 09:37 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
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 Felix Botner univentionstaff 2016-08-22 16:27:31 CEST
Our app containers have names like "fervent_bohr". Why not use the app id as container name.
Comment 1 Dirk Wiesenthal univentionstaff 2016-09-22 06:26:40 CEST
Currently, this should be possible. At some point we intended to start a second container along the original one during an upgrade. Therefore I did not do that.

Except for some raw docker operations, the most common ones can be used by
  univention-app {stop,remove,shell} appid
Comment 2 Erik Damrose univentionstaff 2018-07-03 09:37:57 CEST
I also would like this feature, especially when multiple docker apps are installed. Currently, i have to list all docker containers with docker ps -a and look for the correct one, usually by checking which image the container is based upon.

To avoid the same name for the container, the app version could be part of the container name.