When one tries to copy in a binary in a Dockerfile that has some file capabilities set, then those capabilities are lost during the copy. This requires the Dockerfile author to RUN setcap </path/to/binary> and doing that results in a copy up of the file essentially doubling the storage required to store the binary. This can be avoided if the file capabilities are applied during COPY/ADD saving disk space.