3 ms·

docker-slim is the wrong solution for container optimization. You can't just have a program rm -rf files that it didn't think were in use. What if you missed a

• bigpod 4y ago
  use --include-path to ensure its in
• hnarn 4y ago
  Why did you link a tweet to someone saying they “feel like [they] should do a blog about docker-slim at some point”? What does this contribute?
  • mplewis 4y ago
    This is a Twitter thread that continues below at the following tweet: https://twitter.com/ariadneconill/status/1506483943352250371 https://twitter.com/ariadneconill/status/1506483943352250371 Sorry – I forgot that the Twitter UI doesn't always lend itself to proper threading.
• fwip 4y ago
  I know your question was rhetorical, but probably depends on how mission-critical the code path is (and the consequences of hitting those missing files). If you're running a website and the removed dependency is related to a feature that is uncommon enough that isn't covered by your automated tests, maybe .1% of your users experience a broken page. If you're running critical infrastructure and the removed dependency has to do with leap-second handling, maybe eight months from now, everything crashes and you lose millions of dollars.
• kylequest 4y ago
  Please explain how it's wrong without simply saying you prefer other solutions, which was the case with Ariadne :) Dead code elimination is a common construct in software engineering. There's nothing magical about apps and their dependencies. They are relatively straight forward to identify and for the web apps with static assets there are helpers to help you ensure you got everything.