Workaround for Docker images not identifying the true base image

[nishakm]

When using FROM in a Dockerfile, the image that gets pulled from the Docker registry does not identify the images that they may have been based off. The only indication that this actually happens is from the 'history' in the json config file of the Docker container. There is, however, no indentifier for each of the layers in this base image other than the layer sha.

Currently the implementation uses a direct lookup in base.yml. Perhaps we can do something like this:

1. Rather than look up base.yml, look up cache
2. In cache have an optional repo and tag listing
3. Use the base.yml listing for that repo and tag for the right method of getting packages
4. Have a mapping of 'history' and layers to get clues on what commands were used to get the packages

[nishakm]

#41 might be a good solution. The flow might go something like this:

1. For every entry in the snippets library add where the binary might be
2. Get a list of tuples with the package manager and the binary path
3. Go through the list to see whether any of the package managers are in the first layer of the container
4. When one gets found, use the snippets to find the package metadata

There is still a distinction between baseOS package managers and application level package managers. Some name changes in the architecture is needed here for clarity.

[nishakm]

Will be solved if #51 #60 and #61 are solved

[nishakm]

Resolved in #67