<p>GitHub recently released a container registry alongside their package registry. What is the difference? When would it be better to use one or the other? Do we need both?</p>

Jesse Hattabaugh
<p>Packages are generally simple: they are essentially an archive (i.e. zip file) that contains contents (code libraries, application executables, etc.) and a manifest file (json document, xml file, etc) that describes those contents with a package name and version number (at a minimum).
ie:- npm,pip and composer packages.</p>
<p>Container images are also simple, but they're more like an archive (i.e. a zip file) than a package.
ie:- nginx, redis etc</p>
<p>Verdict:- if some libs repetitively used in any project then we can create package and use in project .while for all project based dependencies we need to choose container to run this. Yes we need both.</p>
