Add "Container Name" field so that containers get a real name rather than a guid

[neildeadman]

Is your feature request related to a problem? Please describe.
n/a

Describe the solution you'd like
An additional field that allows the name of the container to be set. For example, File Browser could be FileBrowser but shows as d60543e9-21ee-4a4c-b027-57fc1a89ec67 under 'docker ps'

Describe alternatives you've considered
Could just use the App name field for this

Additional context
Add any other context or screenshots about the feature request here.

[LinkLeong]

We hope that users do not use cli to manage applications, the application name should be indifferent to users.

[neildeadman]

I understand and appreciate your thought process, but I am looking at moving existing containers into CasaOS and I do use the CLI a little. I hope you reconsider.

[LinkLeong]

I'm sorry for the trouble you've caused. Our team is discussing internally about importing docker applications into casaOS, but will not deal with container names for now.

Or you can let me know what you want to change the container name for, so that we can solve the problem better!

[ajnart]

I'm sorry for the trouble you've caused. Our team is discussing internally about importing docker applications into casaOS, but will not deal with container names for now.

Or you can let me know what you want to change the container name for, so that we can solve the problem better!

I think having the container name be the "Service Name" by default, or the image name would be a great idea. It would be useful for users like me that use SyncThing to synchronize their app configs to the cloud (or that just want to import previous installations of Sonarr/Radarr/...)

[jerrykuku]

This feature has been implemented in v0.3.1. If there are still problems you can reopen this issue.