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
{{ message }}
Repository navigation
Use a more secure base-image for the Solr Operator docker image #294
The security report for the Solr Operator Docker image on it's ArtifactHub page is not very good. This is due mostly to the fact that the base image contains multiple known vulnerabilities.
The current base image is gcr.io/distroless/base:debug-nonroot, and the vulnerabilities come from the fact that we are using the base image, not because it's a debug image. If we instead use gcr.io/distroless/static:debug-nonroot, these vulnerabilities go away.
The base image isn't the whole story. Some of the GoLang libraries that the Solr Operator depends on contain vulnerabilities as well, however removing those will require an upgrade of Kubernetes versions which we cannot currently do. Solving the base-image is the first, and larger, step.
Activity
HoustonPutman commentedon Jul 21, 2021
The difference between
distroless/baseanddistroless/staticis mainly for the purpose of includinglibcfor go programs that usecgo, such as through thenetpackage.Since the Solr Operator is built with
CGO_ENABLED=false, we do not needlibc, so we should be find to base our image ondistroless/static.Kubebuilder uses
distroless/staticby default, so we should be safe with DNS resolution and Certificates when communicating within Kubernetes.