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
{{ message }}
This repository has been archived by the owner on Oct 18, 2022. It is now read-only.
Almost all images derivate from image id 511136ea3c5a (which could be labelled scratch, because it's the one choosen when using FROM scratch). At least since some docker version 0.x if I'm not mistaken.
And recently, the ubuntu image b7cf8f0d9e82 (tags: ubuntu:14.04ubuntu:14.04.2ubuntu:latestubuntu:trustyubuntu:trusty-20150320) didn't derive from "scrach".
Is it a bug in the image creation process ? Or a new direction/convention about root images ?
The text was updated successfully, but these errors were encountered:
As of Docker 1.5.0 (specifically, moby/moby#8827), FROM scratch is a no-op in the Dockerfile, and will not create an extra layer in your image (so a previously 2-layer image will be a 1-layer image instead).
Almost all images derivate from image id
511136ea3c5a
(which could be labelled scratch, because it's the one choosen when usingFROM scratch
). At least since some docker version 0.x if I'm not mistaken.And recently, the ubuntu image
b7cf8f0d9e82
(tags:ubuntu:14.04
ubuntu:14.04.2
ubuntu:latest
ubuntu:trusty
ubuntu:trusty-20150320
) didn't derive from "scrach".Is it a bug in the image creation process ? Or a new direction/convention about root images ?
The text was updated successfully, but these errors were encountered: