4 ms·
If you look at the build, yea, it includes everything and kitchen sink. No one cares to parse it down because in most cases, the big GPU servers running this ha
by stackskipton 3y ago
If you look at the build, yea, it includes everything and kitchen sink. No one cares to parse it down because in most cases, the big GPU servers running this have plenty of hard disk space and since it's a long running container image in most cases, the pull time isn't considered big enough problem for most people to fix.
Prime example of "Hardware is cheap and inefficiencies be damned"
- teaearlgraycold 3y agoIf only it was viable to analyze which files get used. Then cut down the image to just what’s needed.
- dpkirchner 3y agoI can show you some of the big, unnecessary files: all the .a files in /usr/local/cuda* (unless you're building software inside your container). That's, IIRC, at least a gig.
- nurple 3y agoLook at the stargazing snapshotter if you have access to deploy it. I pulls small blobs of the image as they're used by the host, and it tries to use heuristics to put startup data in the initial blob. https://github.com/containerd/stargz-snapshotter https://github.com/containerd/stargz-snapshotter