DockerSlim – Optimize Your Containerized App Dev Experience

dockersl.im

28 points·gilad··4 comments

I'm curious how others are using the recently added support for compose. Happy to answer any questions you might have.

Sounds interesting. I'm wondering how it works.

I tried it on a few images and got inscrutable errors, though.

What kind of images do you have? App images or base images? What's the stack for your image if it's an app image? Is it a server app or a cli app? Do you mind sharing your failures?

By the way, have you looked at the examples? https://github.com/docker-slim/examples Wonder which example is close enough to what you have.

Depending on the command you choose (e.g., "build" or "xray") it's doing different things. With "xray" it's all static analysis where it saves the images and then it analyses it internals. With "build" it performs static and dynamic analysis where it creates a temporary instance of your container. By default, it assumes it's a server app and it'll try to probe your server app when it's running.

I ran build on an app component image in our stack that runs Java. The error:

cmd=build info=container id='81b1a416016ee571209338206bffcf8925b5642a41b4921a2ebde35e10e9047b' status='created' name='dockerslimk_67078_20211230031317' time="2021-12-29T22:13:18-05:00" level=fatal msg="docker-slim: failure" error="API error (400): OCI runtime create failed: container_linux.go:380: starting container process caused: exec: \"/opt/dockerslim/bin/docker-slim-sensor\": stat /opt/dockerslim/bin/docker-slim-sensor: no such file or directory: unknown" stack="goroutine 1 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x88\ngithub.com/docker-slim/docker-slim/pkg/util/errutil.FailOn({0x100d93960, 0x140006a6030})\n\tgithub.com/docker-slim/docker-slim/pkg/util/errutil/errutil.go:28

Reply on news.ycombinator.com