CLI preview about portainer

[Redsandro]

This feature should extend to currently running containers that may or may not have been created/started with portainer. A command line that recreates the current container exactly (e.g. including volume mapping).

It would be nice to to have a button called "show command line" on the overview page with the start/stop buttons that shows a simple dialog with a "copy to clipboard" button that has the following text:

docker run  \
	-d \
	--name <name> \
	-p <port1> \
	-p <port2> \
	-e <environment1> \
	-e <environment2> \
	-v <volume1> \
	-v <volume2> \
	<image>;

[weendigo]

This would be helpful to me in case of running same containers on multiple machines.
Or as it happened to me already, I've set up a container and forgot how...
I'm not really a Docker expert so I'd appreciate having a visual clue here.

[deviantony]

Agree that this should actually be available on details view as well.

[NemesisRE]

I would love that feature.
I had a problem while recreating a container within portainer but the old container was already deleted so all my settings were lost. With that feature one could actually backup the configuration.
Additionally it would help to update the portainer container itself.

[horacecar]

are we having any update here?

[deviantony]

We should put a button next to create/cancel in the container creation view to retrieve the current form result as a docker command in the pastebin.

[beruic]

There is a stackoverflow question on this matter: https://stackoverflow.com/questions/32758793/how-to-show-the-run-command-of-a-docker-container/32774347

Essentially it should be doable by running

$ docker run -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike YOUR-CONTAINER

Just tried it out. It does add some extra stuff, but that is easily removable.

[shalak]

This feature would be great for educational and README-creating purposes. I can configure the container completely in Portainer, then copy-paste the exact command someone else needs to start the container on their own.

[gauteg]

Not to mention that this feature would be a easy way to upgrade the docker container with the running portainer inside it :)
(I am of course open to a update feature I have totally missed...)

[byteduty]

I agree with the above comments. This seems a major hole in functionality. It's a real headache when your trying to migrate persistent docker containers between systems, etc. All the information is available.

[mikhail-gaponov]

I vote for this feature too.
My use case here is to run specific configuration command for container (with currently mapped volumes). By default, this container starts the service (UpSource, to be clear), but when I need to reconfigure base URL, I have to restart this container with specific command and it would be nice to have the whole docker command for CLI.
Another case is to run container with the same configuration on particular environment (not managed by current Portainer installation)

[foundObjects]

I'd very much like to see this feature implemented as well. It would make re-creating containers on other machines not managed by portainer significantly easier.

[Roemer]

That feature would be great. I had several problems (mostly with instable network connections) where re-create failed but the old container got deleted. Having this feature I could just copy the generated command line as fallback if portainers re-create fails.

[Leosirth]

Hi,

I don't know if feasible, but having also an option to "export" a container configuration as a docker compose file (even if not started with a compose itself) would be great.

I have several old container created without a compose file that would like to migrate/backup and this feature would came in hand.

Thanks and regards,

Hi there @Leosirth there is already discussion for a feature that might introduce this functionality here: #2845

[mariyam-portainer]

These are really great points and thanks taking the time to mention them. This is something we will need to discuss and work out.

[ozdeadmeat]

The ability to export a container configuration that has been modified in portainer is a massive hole in portainers capability. Especially for non-experts who are trying to learn docker and use portainer.

Please provide us the ability to export the config either from portainer itself or from the CLI please.

[36grad]

I would also love to see this feature. For me it would make documentation so much easier.

[sindri121]

Aggreged this feature would be of grate help