You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do not have experiences with Dockerslim ourselves but only heard of it.
In general, Shipwright builds images as defined in its build strategy and the image that is produced can very likely also be targeted with dockerslim. But this would happen outside of Shipwright.
Thinking about having it integrated into Shipwright or a build strategy, we are seeing mainly the obstacle that dockerslim requires to run a container to determine which parts are needed, and it may even send http calls therefore that. As Shipwright runs inside a Kubernetes cluster, we have no immediate idea how this would work.
But we can keep this issue open and if somebody wants to investigate on that and finds a solution, then this can be interesting.
Is it possible to reduce the size of the image that shipwright helps in building - using Dockerslim - https://github.com/docker-slim/docker-slim
The text was updated successfully, but these errors were encountered: