You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I commit a container as a new image, and then I run this new image, all data that I saved in the original container are lost/erased.
How can I commit a container without to loss all data?
The text was updated successfully, but these errors were encountered:
cbadillac
changed the title
Data is lost when a postgres container is commited has a new image.
Data is lost when a postgres container is commithas a new image.
May 18, 2018
cbadillac
changed the title
Data is lost when a postgres container is commithas a new image.
Data is lost when a postgres container is commit has a new image.
May 18, 2018
Containers have a read/write layer that is temporary, when the container is 'stopped' it will retain data in that layer, when it's removed and started back up; you're doing so from the image which hasn't been modified. So you'd want volumes mounted from the host onto the container.
When I commit a container as a new image, and then I run this new image, all data that I saved in the original container are lost/erased.
How can I commit a container without to loss all data?
The text was updated successfully, but these errors were encountered: