dockerTools - buildImage vs buildLayeredImage (cp vs ln?)

Is it intentional that when building a sinlge layered image with buildImage some binaries and files are copied over to /bin - while buildLayeredImage does create symlinks in it’s last layer?

Every copied files seems to consume double the space as per my analysis with dive.

  • Am I maybe missing out on something?
  • Might this be a bug? (or rather undesired behaviour?)

Not specific to Docker but I think it’s always preferable to symlink to other store entries.

It better tracks the runtime closure.
I would think it’s a bug anytime (most times) a cp is done rather than ln

No, i don’t think this is intentional and a PR would be welcome :wink: