3 ms·
It seems like this tool is built upon the assumption that the containerized program will load libraries and read files while this tool is tracing it. It seems
by alpb 7y ago
It seems like this tool is built upon the assumption that the containerized program will load libraries and read files while this tool is tracing it.
It seems like the biggest FAQ item is missing from the readme: What happens is my container reads a file only every so often and this tool doesn't capture it?
Also, do I need to keep images running for a while for this tool to minimize the files in the rootfs? It seems impractical, especially in headless environments like CI/CD.
- Operyl 7y agoIt seems they do try and solve this, but potentially not completely depending on what triggers your file load. It seems to be able to simulate HTTP traffic.
- kylequest 7y agoThe temporary containers usually don't run for too long. The probes (http, for now) are there to ensure that the app/services gets to do something useful exercising different code paths. Still, it is possible that something could be missing or you might want to keep something extra. For those cases you can tell docker-slim what else you want to keep in your container image (it has a few flags for that).