Command Line Interpreter

[thesugarat]

Is your feature request related to a problem? Please describe.
I start 99% of my containers from the command line and then manage from Portainer. I do this because all websites use a command line startup I.E. "docker run -d -p 9000:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer", however the Portainer interface has all of these options in different places in the gui. I then save all the "start lines" so that I can spin them up the same way later on or in a different VM.

Describe the solution you'd like
I would like to see a way to save the text start lines in a Portainer library, and more importantly there should be a Command Line Interpreter where you can enter the start line in text format into a box and upon hitting an Evaluate button it should autopopulate the various sections of the Portainer GUI for creation of a Container. Then hitting Deploy would create the same container as starting from the command prompt/bash, and would aid in learning the Portainer GUI and how the different portions of the start line are entered. This would also aid in converting Docker Hub start lines into running containers for newcomers to Portainer. The ability to export/share your unique or tweaked start lines would be as simple as copying and pasting to/from the Library.

Describe alternatives you've considered
There are no alternatives to this other than saving the start lines in a text file and creating all containers from the command prompt/bash.

[WWoodpecker]

Yes, a "Docker run to Compose syntax converter" like in Dockge would be great.

[webysther]

Yeap, if Dockge start support multiple servers I will migrate, I manage my stacks using only portainer with the API and today with 50+ stacks is terrible, is so basic if the process broke portainer can't deal with *_old folder and no update on this for at least 3 years...