From 07a013d9233f6ece6ee167c4fa98fde172843d10 Mon Sep 17 00:00:00 2001 From: Arnaud Porterie Date: Thu, 14 Jan 2016 15:35:39 -0800 Subject: [PATCH] Updated Engine v1.10.0 content addressability migration (markdown) --- Engine-v1.10.0-content-addressability-migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Engine-v1.10.0-content-addressability-migration.md b/Engine-v1.10.0-content-addressability-migration.md index 84c25b6..732fd8d 100644 --- a/Engine-v1.10.0-content-addressability-migration.md +++ b/Engine-v1.10.0-content-addressability-migration.md @@ -1,5 +1,3 @@ -# Docker Engine 1.10 migration - TL;DR; - More secure foundation for referencing images and layers @@ -7,6 +5,8 @@ TL;DR; - Upgrading old images will include a migration step - A migration tool exists in order to minimize migration time +## Understanding 1.10 migration + This post describes the upcoming changes to the way Docker Engine stores images and filesystem data in containers. These changes are coming to users starting from version v1.10. (FIXME: link to download rc1) Starting from v1.10 we completely change the way Docker addresses the image data on disk. Previously, every image and layer used a randomly assigned UUID, now we have implemented a content addressable method using an ID that is based on a secure hash of the image and layer data.