Study the benefit of using a binary data tool to embed resources
imulab opened this issue · 2 comments
@requaos proposed a binary data tool pkger in #38
The original intention was to avoid too many COPY commands creating too many layers. The stock files were since placed in a single folder, reducing the total number of COPY commands needed to 2 (1 for binary, 1 for public folder).
However, the use of binary data tool may still be beneficial, if:
- It reduces
COPYcommands even more - It does not add too much complexity to the building process (requiring external software be installed)
- It can help resource references in tests. Currently tests reference files in their relative paths, which is a fragile practice. It will be much better to be able to reference absolute paths from the root of the module.
@imulab The primary benefit of using a binary data tool is the ability to have the final container be
FROM scratch
This allows for minimal container size and reduces attack surface from a security standpoint.
In production circumstances I will usually upx -9 my go binary, that is compiled with the -netgo flag to remove dependencies on an os level networking stack. Results in a <5Mb container that deploys like lightning.