Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by jvdongen on Saturday April 27, 2019 @05:39AM
(#19764718)
Exactly this. For the docker images we use in production, we fork the corresponding git repo, build our own image and push it to our own local docker registry and pull it from there. It's fairly easy to setup in fact.
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by Boulth on Saturday April 27, 2019 @05:44AM
(#19764730)
Out of curiosity do you resolve it so that the image is FROM scratch or do you rely on alpine/some other base image?
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by kobalsky on Saturday April 27, 2019 @12:12PM
(#19766213)
I forked an ubuntu image and then used it as a base for all my projects. It doesn't come for free though, you will need to periodically run security updates and then rebuild all images that depend on it.
Actually only short names go to docker hub, one can setup their own registry and use it via dns names.
Example: docker pull quay.io/letsencrypt/letsencrypt