4 ms·

> Also, containers build on other containers. E.g. the highly popular phpmyadmin or nextcloud images build on top of php. So each "nextcloud" pull, will result

by hiatus 2y ago

> Also, containers build on other containers. E.g. the highly popular phpmyadmin or nextcloud images build on top of php. So each "nextcloud" pull, will result in a pull for php too. Are those developers? Does that mean hundreds of millions less pulls? When pulling images from dockerhub that are based on other images, the image is rebuilt from scratch each time? That doesn't sound right.

0points 2y ago
> the image is rebuilt from scratch each time? That's not what parent is saying. A Dockerfile usually start off with a base image, like: FROM php This will pull the php base image, which is already built and published, from dockerhub. I guess this makes sense if you are familiar with Docker.
- hiatus 2y ago
  Yeah but the dockerfile that builds the wordpress image or whatever is not being recreated/rebuilt with every pull of wordpress.
  - 0points 2y ago
    Yes, you seem to be grasping this.
shagie 2y ago
Layers are pulled. If foolang image has: layer c layer d layer e And then fooadmin image is FROM foolang:latest (and the more stuff) and builds the layers: layer f layer g ... then a user pulling fooadmin pulls layers g,f,e,d,c,b,a (b and a being layers provided by the image that foolang was built on top of). The question is then "does the pull of layer e in docker pull foo admin count as part of docker pull foolang?"
- hiatus 2y ago
  > The question is then "does the pull of layer e in docker pull foo admin count as part of docker pull foolang?" It doesn't.