3 ms·
because you might want to deliver it in its "nest", i.e., a filesystem with resources the go binary wants to access at runtime
by jjtheblunt 6y ago
because you might want to deliver it in its "nest", i.e., a filesystem with resources the go binary wants to access at runtime
- pjmlp 6y agoOn proper desktop OS those resources are embedded in the binary.
- jjtheblunt 6y agoagreeing with your comment, and a coffee epiphany resulted: it also made me realize that the container IS such a beast, as it's a binary file format that is handled by a different linker-loader, that which takes such a binary file, extracts the runnable content and runs it in a mounted bundled filesystem.