Closed jakirkham closed 8 years ago
parente
commented
8 years ago :+1:
The interactions aren't that complex from a Docker inheritance standpoint. The max-depth of the tree is 2. But, to your point, it's good to depict that.
I'm also wondering if less popular images should be culled over time to reduce the maintenance and complexity cost. For example, r-notebook has been pulled from Docker Hub about 100 times total. In contrast, all-spark-notebook has been pulled 166,000 times.
jakirkham
commented
8 years ago The interactions aren't that complex from a Docker inheritance standpoint.
Sure there is no multiple inheritance. So, simple tree.
The max-depth of the tree is 2.
Of our tree? Sure.
I'm also wondering if less popular images should be culled over time to reduce the maintenance and complexity cost. For example, r-notebook has been pulled from Docker Hub about 100 times total. In contrast, all-spark-notebook has been pulled 166,000 times.
Yes, generally, taking stock is a good idea, as well.
I think I recall seeing the pushes were counted in the total at some point. I don't know if it was intentional or not. Also, this was awhile ago so this behavior could have been corrected.
parente
commented
8 years ago Assuming all the outstanding PRs about singleuser and pyspark/all-spark unification go in, how about this?
which is the source for:
willingc
commented
8 years ago Very pretty. I sent another PR to move it up the page #172
Maybe this is somewhere and then a good nudge in the right direction would be great.
I think it would be really nice to have a diagram that shows us how the different images here are related. It seems like we have quite a few and it would really help to understand which images are affected by making a change in one Dockerfile. It could probably be some SVG so it shows up nicely in the browser (even mobile) and we could embed it in the top level Readme. Thoughts?