# \[Resolved\] Unable to Execute zrok in shell on pi 4

**URL:** <https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082>\
**Category:** zrok\
**Created:** [February 14, 2023, 6:51pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082 "2023-02-14T18:51:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThaneVim](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@ThaneVim](https://openziti.discourse.group/u/ThaneVim)\
**Post date:** [February 14, 2023, 6:51pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/1 "2023-02-14T18:51:38Z")

</div>

No matter if I add it to my path per the docs, move the executable to /usr/bin and launch, or just launch from the extracted location, I always get `-bash: ./zrok: No such file or directory`  
 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/2ae8508de3f27c5a7811c34ce84009360d430109.png)

This is on a Pi 4, running the latest Raspberry Pi OS, with the arm version of zrok downloaded and extracted to a previously-empty and dedicated folder.The error persists even if I run `chmod +x zrok`. The current permissions for the zrok executable is `-rwxr-xr-x`.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [February 14, 2023, 6:57pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/2 "2023-02-14T18:57:31Z")

</div>

Hi @ThaneVim, thanks for the post and welcome the `zrok` and the community!

I was able to reproduce that problem using a different arm7 archetecture. Looking at the file it’s marked as:

```auto
file zrok
zrok: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, BuildID[sha1]=1de051ff17e566be3c066cba101bda11a095d222, for GNU/Linux 3.2.0, stripped

```

We’ll have to take a look. We’ll follow up in a bit

---

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [February 14, 2023, 7:21pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/3 "2023-02-14T19:21:01Z")

</div>

Hi @ThaneVim , Will you try the 64bit download on your Pi 4?

[https://github.com/openziti/zrok/releases/download/v0.3.1/zrok\_0.3.1\_linux\_arm64.tar.gz](https://github.com/openziti/zrok/releases/download/v0.3.1/zrok_0.3.1_linux_arm64.tar.gz)

---

<div class="post-metadata">

**Author:** ![ThaneVim](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@ThaneVim](https://openziti.discourse.group/u/ThaneVim)\
**Post date:** [February 14, 2023, 7:23pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/4 "2023-02-14T19:23:43Z")

</div>

That worked! Not sure how I missed that release on the releases page, but it is now running on my Pi. Thanks!!

---

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [February 14, 2023, 7:33pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/5 "2023-02-14T19:33:45Z")

</div>

Do you know if you’re running 64bit RasPi OS? What does `uname -m` say?

---

<div class="post-metadata">

**Author:** ![ThaneVim](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@ThaneVim](https://openziti.discourse.group/u/ThaneVim)\
**Post date:** [February 14, 2023, 7:54pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/6 "2023-02-14T19:54:54Z")

</div>

It is 64-bit, with `uname -m` returning `aarch64`.

And I knew that, but for some reason just glazed over the arm64 release on the releases page for Zrok, opting to download the regular arm version. Everything is working properly with the arm64 version downloaded. I think I just read arm64 as amd64? Either way, my failing.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [February 14, 2023, 7:56pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/7 "2023-02-14T19:56:00Z")

</div>

Sadly, it caught me too! 🙂 I had downloaded the arm7 build and didn’t realize it… Thanks @qrkourier for straightening us both out!

---

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [February 14, 2023, 7:57pm UTC](https://openziti.discourse.group/t/resolved-unable-to-execute-zrok-in-shell-on-pi-4/1082/8 "2023-02-14T19:57:34Z")

</div>

Thanks for the info. Good luck with zrok!
