How to patch eck-operator image

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi there,

I need to do some security update of the eck-operator image.
Usually I run a docker image and with --entrypoint /bin/bash, just like
docker run -it --entrypoint /bin/bash image
and do the update there. Then commit the updated container as a patched image.
But when I do this to eck-operator, I got a error here:
"Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "/usr/bin/sh": stat /usr/bin/sh: no such file or directory": unknown."

I exec into a running operator, there is /bin/bash, but why do I get such error.
Any idea about it or is there other ways to do the update?
Thanks

2

Is that because eck-operator is using distroless base?

3

Yes!

Since 1.2.0, the ECK operator container image is much smaller and more secure thanks to switching to Distroless as the base image.

This should save you from having to perform security updates to the ECK operator container image.