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?

  • Docker-Compose Elkstack
  • Getting “can't cd” error when when building using dockerfile
  • docker-compose does not launch
  • Docker registry on EC2
  • DockerHub Automated Build Failure
  • What is the cost of a container?
  • Any way to suspend/resume WildFly docker container?
  • Docker containers-ID got change on each startup of container
  • How to perform checkpoint and restore of docker containers across two hosts?
  • ENTRYPOINT with environment variables is not acepting new params
  • Kubernetes plugin containers can't connect back to Jenkins
  • Issue with docker-py in executing /bin/bash
  • 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.