# Install-ose.sh script throws "no such file or directory" error

**URL:** <https://forums.screenly.io/t/install-ose-sh-script-throws-no-such-file-or-directory-error/625>\
**Category:** Anthias\
**Created:** [September 28, 2021, 5:25pm UTC](https://forums.screenly.io/t/install-ose-sh-script-throws-no-such-file-or-directory-error/625 "2021-09-28T17:25:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![miktho76](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@miktho76](https://forums.screenly.io/u/miktho76)\
**Post date:** [September 28, 2021, 5:25pm UTC](https://forums.screenly.io/t/install-ose-sh-script-throws-no-such-file-or-directory-error/625/1 "2021-09-28T17:25:57Z")

</div>

Fresh raspbian lite install. When I run the install script:

```auto
$ sudo bash <(curl -sL https://www.screenly.io/install-ose.sh)

```

It immediately throws a “/dev/fd/63: No such file or directory” error.

I’m unable to manually create the directory either, so I’m guessing this is maybe a permissions issue?

Honestly, I’d prefer to just install a screenly image, but the files from [here](https://github.com/Screenly/screenly-ose/releases) are not .img/.iso and there are zero instructions on how to flash a tar.gz file as a bootable image… or what the difference between QT or Webview is…

---

<div class="post-metadata">

**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\
**Post date:** [June 9, 2026, 8:16am UTC](https://forums.screenly.io/t/install-ose-sh-script-throws-no-such-file-or-directory-error/625/2 "2026-06-09T08:16:41Z")

</div>

That old install script has been retired, which is why it errors out. Installing is much simpler now: Anthias is available directly in the Raspberry Pi Imager, so you choose Anthias from the operating system list and write it to your SD card. Marking this as solved. If you prefer installing on top of Raspberry Pi OS Lite, the current steps in the project README cover that too.