[Camel-K]: It cannot start due to "exec: \"kamel\": executable file not found in $PATH"

[Luca Morandini <lu...@gmail.com>]

Folks,

I built Camel-K from the latest master branch, but was not able to
make it start on a Kubernetes cluster:
<<
Error: failed to start container "camel-k-operator": Error response
from daemon: oci runtime error: container_linux.go:247: starting
container process caused "exec: \"kamel\": executable file not found
in $PATH"
Back-off restarting failed container
>>

Needless to say, the executable seems to be in the image when I try to
'docker run' it (the image can be found at
docker.io/lmorandini/camel-k:1.0.0-M2-SNAPSHOT).

Any help appreciated,

Luca Morandini

Re: [Camel-K]: It cannot start due to "exec: \"kamel\": executable file not found in $PATH"

[Luca Morandini <lu...@gmail.com>]

> Hi,
> I've updated the master to use M3-SNAPSHOT, since we've cut a release of M2
> last saturday.

That did the trick, thanks a lot.

Cheers,

Luca Morandini

Re: [Camel-K]: It cannot start due to "exec: \"kamel\": executable file not found in $PATH"

[Nicola Ferraro <ni...@gmail.com>]

Hi,
I've updated the master to use M3-SNAPSHOT, since we've cut a release of M2
last saturday.

I've run:
$ make images
$ docker run apache/camel-k:1.0.0-M3-SNAPSHOT kamel version -n x
Camel K Client 1.0.0-M3-SNAPSHOT

So the `kamel` binary seems to be in the right place. Are you using `make
images` or a different command to build the image?

We've recently introduced some changes to merge all binary files into the
single one (`kamel`): https://github.com/apache/camel-k/pull/966
So the operator launch script is now `kamel operator` (check the
deployment, in case uninstall + reinstall).

Nicola

On Mon, Oct 7, 2019 at 9:41 AM Luca Morandini <lu...@gmail.com>
wrote:

> Folks,
>
> I built Camel-K from the latest master branch, but was not able to
> make it start on a Kubernetes cluster:
> <<
> Error: failed to start container "camel-k-operator": Error response
> from daemon: oci runtime error: container_linux.go:247: starting
> container process caused "exec: \"kamel\": executable file not found
> in $PATH"
> Back-off restarting failed container
> >>
>
> Needless to say, the executable seems to be in the image when I try to
> 'docker run' it (the image can be found at
> docker.io/lmorandini/camel-k:1.0.0-M2-SNAPSHOT).
>
> Any help appreciated,
>
> Luca Morandini
>