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
I don't think we should recommend docker commit and docker push as the way to 'publish' a Dockerfile. This results in just a binary image blob being uploaded to the hub, which is not particularly transparent; a user really has no way of knowing / trusting that the image contains what it says.
I think it would be better to simply put the Dockerfile on Github and link it as an automated build. (In this case, users should probably use one of the version-specific tags instead of :latest in their FROM line to ensure long-term reproducibility / stability of the build).
The text was updated successfully, but these errors were encountered:
I don't think we should recommend
docker commit
anddocker push
as the way to 'publish' a Dockerfile. This results in just a binary image blob being uploaded to the hub, which is not particularly transparent; a user really has no way of knowing / trusting that the image contains what it says.I think it would be better to simply put the Dockerfile on Github and link it as an automated build. (In this case, users should probably use one of the version-specific tags instead of
:latest
in theirFROM
line to ensure long-term reproducibility / stability of the build).The text was updated successfully, but these errors were encountered: