Add "Container Name" field so that containers get a real name rather than a guid about casaos HOT 5 CLOSED

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

from casaos.

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

from casaos.

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.

from casaos.

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!

from casaos.

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/...)

from casaos.