# Cannot find KONG executable in bin dir

**URL:** https://discuss.konghq.com/t/cannot-find-kong-executable-in-bin-dir/3420
**Category:** Questions
**Created:** [April 30, 2019, 4:41am UTC](https://discuss.konghq.com/t/cannot-find-kong-executable-in-bin-dir/3420 "2019-04-30T04:41:42Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![duybinh0208](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@duybinh0208](https://discuss.konghq.com/u/duybinh0208)
#### Post date: [April 30, 2019, 4:41am UTC](https://discuss.konghq.com/t/cannot-find-kong-executable-in-bin-dir/3420/1 "2019-04-30T04:41:43Z")

</div>

I have had a problem with `KONG` executable when instaling from the source. The installation finished without any errors; however, I cannot find the `KONG bin dir` even though I have set the `LUA_PATH`, `LUA_CPATH`.

The command I’ve used to install to install `KONG` into `~/software/kong123` dir:

> luarocks install --tree ~/software/kong123 kong 1.0.3 OPENSSL\_DIR=$OPENSSL\_HOME OPENSSL\_LIBDIR=$OPENSSL\_HOME/lib CRYPTO\_DIR=$OPENSSL\_HOME

The output:

> kong-prometheus-plugin 0.3.4-2 is now installed in /home/mpe/software/kong123 (license: Apache 2.0)
> 
> Cloning into ‘kong’…  
> remote: Enumerating objects: 704, done.  
> remote: Counting objects: 100% (704/704), done.  
> remote: Compressing objects: 100% (596/596), done.  
> remote: Total 704 (delta 152), reused 281 (delta 83), pack-reused 0  
> Receiving objects: 100% (704/704), 765.92 KiB | 0 bytes/s, done.  
> Resolving deltas: 100% (152/152), done.  
> Note: checking out ‘e7e2fa3a6e8e325d1eded180438f2ea81aaa28ee’.
> 
> You are in ‘detached HEAD’ state. You can look around, make experimental  
> changes and commit them, and you can discard any commits you make in this  
> state without impacting any branches by performing another checkout.
> 
> If you want to create a new branch to retain commits you create, you may  
> do so (now or later) by using -b with the checkout command again. Example:
> 
> git checkout -b new\_branch\_name
> 
> kong 1.0.3-0 is now installed in /home/mpe/software/kong123 (license: Apache 2.0)

Check `bin` dir inside `kong123` dir but there’s no any `kong` executable:

> $ ll ~/software/kong123/bin/  
> total 12  
> -rwxr-xr-x 1 mpe mpe 584 Apr 29 23:53 json2lua  
> -rwxr-xr-x 1 mpe mpe 583 Apr 29 23:52 lapis  
> -rwxr-xr-x 1 mpe mpe 584 Apr 29 23:53 lua2json

Also, I see that `luarocks` automatically `clones` the `KONG source code` from `git` but I cannot find where is the location from which the source code was cloned? Perhaps, the `KONG bin dir` is in that location?

> Cloning into ‘kong’…  
> remote: Enumerating objects: 704, done.  
> remote: Counting objects: 100% (704/704), done.  
> remote: Compressing objects: 100% (596/596), done.  
> remote: Total 704 (delta 152), reused 281 (delta 83), pack-reused 0  
> Receiving objects: 100% (704/704), 765.92 KiB | 0 bytes/s, done.  
> Resolving deltas: 100% (152/152), done.

Could you give me some ideas to find a workaround?

Thanks.