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
A bug in docker 1.8 would prevent deletion of an image if a container included a layer referencing an image's topmost layer even though the container was derived from another image that was different but included this same image layer.
To advert this problem, the initial SCRATCH image, used when creating an image's first layer is differentiated by executing MAINTAINER $(basename $(mktemp -u)) resulting in a unique top image layer for each image created by the dkrcp.
As a workaround, use the --change 'MAINTAINER <MaintainerName>' to set the Author field to a desired value.
This workaround strictly applies to Docker 1.8. In derivative Docker versions, dkrcp doesn't execute the MAINTAINER instruction, therefore, the Author field is unassigned.
The text was updated successfully, but these errors were encountered:
A bug in docker 1.8 would prevent deletion of an image if a container included a layer referencing an image's topmost layer even though the container was derived from another image that was different but included this same image layer.
To advert this problem, the initial
SCRATCH
image, used when creating an image's first layer is differentiated by executingMAINTAINER $(basename $(mktemp -u))
resulting in a unique top image layer for each image created by thedkrcp
.As a workaround, use the
--change 'MAINTAINER <MaintainerName>'
to set the Author field to a desired value.This workaround strictly applies to Docker 1.8. In derivative Docker versions,
dkrcp
doesn't execute the MAINTAINER instruction, therefore, the Author field is unassigned.The text was updated successfully, but these errors were encountered: