It can be useful to commit a container’s file changes or settings into a new image. This allows you to debug a container by running an interactive shell, or to export a working dataset to another server. Generally, it is better to use Dockerfiles to manage your images in a documented and maintainable way.
The commit operation will not include any data contained in volumes mounted inside the container.
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. If this behavior is undesired, set the --pause option to false.
Azure Training Syllabus:
DevOps Cloud Architect - 5 Months Free Program - • DevOps Architect Free 5 Months Training | ...
Azure-Cloud-DevOps-Zero-to-Advanced-Free-Training full list - • Azure-Cloud-DevOps-Zero-to-Advanced-Free-T...
Docker-Administration-Zero-To-Hero - • Docker-Administration-Zero-To-Hero
Vijayabalan Balakrishnan
LinkedIn : / vijaystack
See CloudnLoud links at the bottom
Visit :
GitHub: https://github.com/cloudnloud
Facebook : / cloudnloudtech
FacebookGroup : / cloundloudtech
Twitter : / cloudnloud
LinkedIn : / cloudnloud
YouTube : / cloudnloud
Telegram Tech Group - https://t.me/joinchat/GaTlYKfFZEw3YmE1