I know that when you use, for example, docker commit abcdefgh ola/minhaimagem:1.0
you are saving your changes from the abcdefgh container into
As mentioned in docker commit:
By default, the container being committed and its processes will be paused while the image is committed. This reduces the likelihood of encountering data corruption during the process of creating the commit.
That step (waiting for the processes to pause) can take time.
If this behavior is undesired, set the
--pause
option to false.
You can see the actual commit call in api/server/router/image/image_routes.go#postCommit() which is then routed through a backend to daemon/commit.go#Commit()