I started a docker container with –rm Is there an easy way to keep it, without redoing everything?

Is there a quick way to save the state of a docker container started with the –rm flag, as if you didn’t specify it?

  • How can I know why Docker container stopped?
  • Should Swarm Master Join As Node in a Single Node Cluster?
  • what does fd:// mean exactly in dockerd -H fd://
  • Reverse Proxy for golang docker containers
  • Cant build a docker dart-runtime image after a local pub-get
  • Set execution timeout limit while creating docker
  • Efficient development flow for Cloud Foundry
  • How to check if the restart policy works of Docker
  • Getting the manifest list (fat manifest) from docker registry
  • Should Docker be used in a non devops, not very agile environment? [closed]
  • How to run same container on all Docker Swarm nodes
  • Create Docker for Wso2 DAS
  • One Solution collect form web for “I started a docker container with –rm Is there an easy way to keep it, without redoing everything?”

    Only the upcoming 1.10 docker update command would be able to (eventually) do that (cancel a --rm option)

    But the 1.10 version of that command only supports resource configs.
    It will be extended though in the future.

    So for now, this does not seem possible.
    You would have to stop it and relaunch it with the right set of options.

    Note: if the issue is that a volume referenced by that container would be lost if you stopped (and automatically remove) said container, know that you can re-attach that volume to a new container.

    The docker export mentioned by Joachim Isaksson in the comments is one workaround, but it has limitation (ie it won’t export volume)

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.