According to Red Hat, the current best way to secure your Docker usage is to `127.0.0.1 index.docker.io` and use an alternate transport.
The core "translate flags into running container options" works fine IMO, it's the centralized transport causing the issue.
Which isn't the end of the world, as distributing tarballs is not exactly a demanding task.
As an example / plug, I helped write a (prototype) tool that lets you import a docker image from the registry, then transport / version it separately:
https://github.com/polydawn/hroot
Thus, integrating via `docker load` + `docker export` is possible & reasonable.
The core "translate flags into running container options" works fine IMO, it's the centralized transport causing the issue. Which isn't the end of the world, as distributing tarballs is not exactly a demanding task.
As an example / plug, I helped write a (prototype) tool that lets you import a docker image from the registry, then transport / version it separately: https://github.com/polydawn/hroot
Thus, integrating via `docker load` + `docker export` is possible & reasonable.
Linked from the article: https://securityblog.redhat.com/2014/12/18/before-you-initia...