ko VS Lean and Mean Docker containers

Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.

- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile

ko

You don't need to write and manage Dockerfiles. Simply just use ko: https://github.com/google/ko (You also don't need Docker Engine)

Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko

Here is link number 1 - Previous text "ko"

It depends on your use case, but have you ever tried google/ko?

If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.

I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko

And if you want to make the container quickly secure without bloats, maybe give this a try https://github.com/slimtoolkit/slim

Slim.ai presents the data in a more user friendly way than many of the other tools in this post. On top of its open source SlimToolkit for identifying the contents of an image, Slim.ai uses Trivy for vulnerability scanning.

What about https://github.com/slimtoolkit/slim?

A last practice that I do not use at all and which may interest you is to use slim toolkit to keep only the useful elements in your final image.

Anyone tried using https://github.com/docker-slim/docker-slim To minify an image?..

Distroless images are better left for people with serious need for lightweight images and good Linux knowledge because they require lot of planning with the build so that they stay light and work. If you need lighter images but docker isn't your main tool and you can't afford to take hours and hours of practicing different build strategies you can check docker-slim (https://dockersl.im/). With this tool you can easily size down the images.

Maybe this would help in that regard: https://github.com/docker-slim/docker-slim