title: Why does docker container persist changes despite restart
body: <p>I login to <code>ubuntu</code> docker container having name <code>epic_torvalds</code> using <code>docker exec</code> and create a file <code>/tmp/test.log</code></p>
  <p>I then wish to persist this change <code>/tmp/test.log</code> so I do <code>docker commit epic_torvalds newlogimage</code></p>
  <p>Now stopping and starting the containers using <code>docker container rm -f &lt;containerid&gt;</code> for both <code>epic_torvalds</code> &amp; <code>newlogimage</code> shows <code>/tmp/test.log</code> even after restarting the docker daemon.</p>
  <p>My expectation was that the changes to the container once committed are saved in the newly created container and do not persist in the base image from which it was created.</p>
  <p>Only If I delete the image of <code>epic_torvalds</code> and recreate the old ubuntu image using <code>docker run</code> is when the /tmp/test.log is lost.</p>
  <p>Thus, is the changes to a container persisted by default despite restarts without <code>docker commit</code>?</p>
  <p>Is there is a feature not to persist changes to the container if that happens to be the default behavior?</p>