Remove leading / from ENTRYPOINT in minio-operator

Summary

The leading slash to refer to the minio-operator bin in the root directory is changed in our implementation via the Dockerfile in line 7. This needs to be set to minio-operator vs /minio-operator.

Steps to reproduce

1. docker pull registry1.dso.mil/ironbank/opensource/minio/operator:v5.0.3
2. docker run registry1.dso.mil/ironbank/opensource/minio/operator
3. Observe the error.

We can override the ENTRYPOINT to see how it should work:

docker run --entrypoint minio-operator registry1.dso.mil/ironbank/opensource/minio/operator

What is the current bug behavior?

MinIO Operator produces the following error:

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/minio-operator": stat /minio-operator: no such file or directory: unknown.

What is the expected correct behavior?

MinIO Operator will attempt to start but will be missing an argument (e.g. controller) in this specific case; however, we will add the argument via the Helm chart. The output should instead resemble:

NAME:
 minio-operator - MinIO Operator

DESCRIPTION:
 MinIO Operator automates the orchestration of MinIO Tenants on Kubernetes.

USAGE:
 minio-operator [FLAGS] COMMAND [ARGS...]
...

The above is an abridged output of the help page provided by minio-operator.

Relevant logs and/or screenshots

Please see the relevant message pasted above.

Possible fixes

Remove the leading slash. This fix worked for me locally.

ENTRYPOINT ["minio-operator"]

Tasks

• Bug has been identified and corrected within the container

Please read the Iron Bank Documentation for more info