botkube: bad entrypoint
disconn3ct opened this issue · 0 comments
disconn3ct commented
Details
What steps did you take and what happened:
$ docker run --rm -ti raspbernetes/botkube
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown.
What did you expect to happen:
Successful startup.
Anything else you would like to add:
Per the docs, ENTRYPOINT /go/bin/botkube
invokes the "shell" pattern and results in:
ENTRYPOINT ["/bin/sh","-c","/go/bin/botkube"]
To use bare containers, it needs to use the exec form:
ENTRYPOINT ["/go/bin/botkube"]
Note: Miscellaneous information that will assist in solving the issue.
Additional Information:
Note: Anything to give further context to the bug report.