PHP binary not found at specified path: /usr/local/sbin/php. Please ensure PHP is installed.

[inpresif]

Hi,

Never seen this issue before. Did a fresh install of Wave3 with Docker.
PHP is installed but not in sbin, just the regular /usr/local/bin/php.

Tried adding this in .env, no luck.
PHP_BINARY=/usr/local/bin/php

Is there any particular thing I need to change to be able to use this? Sorry I'm more of a vanilla PHP person, trying Wave for the First time.

Thanks.

[bobbyiliev]

Hey @inpresif! 👋

Wave is indeed just a Laravel app, so it's mostly PHP under the hood.

That error usually happens when Laravel can't find the PHP binary at the expected path. As you are using Docker, can you share your Dockerfile here? It is possible that something in there might be missing.

Welcome to Wave! 🚀

- Bobby

[inpresif]

Hey!

Thanks for the extra details!

As far as I can seem for some reason the app is looking for the PHP binary in /usr/local/sbin/php while in your Docker container it's located in /usr/local/bin/php.

Not 100% sure why but a quick fix will be to add a symbolic link in the Dockerfile to make PHP available at the expected path:

RUN ln -s /usr/local/bin/php /usr/local/sbin/php

Let me know how it goes!

On another note, your nginx configuration looks correct, but make sure the Laravel routing is properly handled by updating the location block:

location / {
    try_files $uri $uri/ /index.php?$query_string;
}

• Bobby

Thanks for the symlink tip, I did read thast someplace else as well. However, now it just continues on that same error path, just onto the next thing so I think that even though I can fix this but adding another symlink, I might be on a path of ongoing issues with these kind of - what I consider red flags for the future - warnings:)

Please note composer is installed and works just fine when running: composer install

Composer binary not found at specified path: /usr/local/sbin/php-fpm/composer. Please ensure Composer is installed.

What do you think? I'm sure I must have something setup incorrectly as every other dev project works fine.

EDIT:
I actually added the following line similar to the one above into my Dockerfile and got an error rebuilding, so not sure what is going on here, at all :). No idea where it gets the idea for the URLS/path from that is displayed in the browser.

RUN ln -s /usr/local/bin/composer /usr/local/sbin/php-fpm/composer:

Error:

0.502 ln: failed to create symbolic link '/usr/local/sbin/php-fpm/composer': Not a directory
------
failed to solve: process "/bin/sh -c ln -s /usr/local/bin/composer /usr/local/sbin/php-fpm/composer" did not complete successfully:

EDIT2 (for clarity for future reference/users)

I ran composer install again and after a while (~10m) it did finish. Now I actually do get to the frontpage, be it with a permission error but I'll see and figure that out.

The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened in append mode: Failed to open stream: Permission denied The exception occurred while attempting to log: The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened in append mode: Failed to open stream: Permission denied The exception occurred while attempting to log: installed.json does not exist at: /var/www/html/resources/plugins/installed.json Context: {"exception":{}}

EDIT3:

After gettinh the things in edit2 going, I entered into some new issues. Rebuilding my Docker image creates an error that only got resolved after compketrely deleting the entire WAVE/Laravel folder again.
The error is:

------
 > [php internal] load build context:
------
failed to solve: archive/tar: unknown file mode ?rwxr-xr-x

Maybe it is due to using Docker Desktop for Windows, not sure. Just letting you know.

Has anybody ran this with Windows Docker Desktop?

Thanks again.

[bobbyiliev]

Hey!

Ah yes, it’s very likely that Docker Desktop for Windows is causing some of these issues. Unfortunately, I don’t have a Windows machine to try and reproduce this on, so I can’t confirm for sure.

However, I can 100% confirm that all the errors you’re seeing are more related to Docker + Laravel setup rather than being specific to Wave itself.

For the permissions issue, you can try adding this to your Dockerfile:

RUN chown -R www-data:www-data /var/www/html/storage

Regarding the Composer issue, I noticed you had commented out the Composer copy command:

# COPY --from=composer:2.3.5 /usr/bin/composer /usr/bin/composer

Uncommenting that line might help fix the issue. On my end, composer install runs in about 2-3 seconds—it’s a standard operation for Laravel.

If you’re still running into random issues, you might want to try Laravel Herd. It’s free and works on Windows too:

Herd

The built-in MySQL feature in Herd is paid, but you can always spin up a separate MySQL Docker container and connect to it instead.

Let me know how it goes! 🚀

[inpresif]

Hi Bobby,

I actually am some steps ahead.
I documented the fix in my personal readme file:

## permission errors after volume sharing?
    docker exec -it php-dev chown -R www-data:www-data /var/www/html/storage /var/www/html/bootstrap/cache

I'm at the Migration step right now, but using MySQL gives me an integrity error

2024_03_29_225928_create_notifications_table ........................................................................................ 52.07ms DONE
  2024_03_29_230138_create_subscriptions_table ........................................................................................ 98.83ms FAIL

   Illuminate\Database\QueryException 

  SQLSTATE[HY000]: General error: 1824 Failed to open the referenced table 'plans' (Connection: mysql, SQL: alter table `subscriptions` add constraint `subscriptions_plan_id_foreign` foreign key (`plan_id`) references `plans` (`id`) on delete cascade)

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:825
    821▕                     $this->getName(), $query, $this->prepareBindings($bindings), $e
    822▕                 );
    823▕             }
    824▕ 
  ➜ 825▕             throw new QueryException(
    826▕                 $this->getName(), $query, $this->prepareBindings($bindings), $e
    827▕             );
    828▕         }
    829▕     }

      +9 vendor frames 

  10  wave/database/migrations/2024_03_29_230138_create_subscriptions_table.php:14
      Illuminate\Support\Facades\Facade::__callStatic("create")

I'll check the migrations folder and look for a fix, but again, just thought you should know and also keeping the journey here documented for future users with similar paths.

[bobbyiliev]

Hey!

Happy to hear that you've got it working this far!

The migration error was already fixed a few weeks ago with this PR here: #138

This is already available in Wave v3.0.1

[inpresif]

Ok, cool. I'll download the new one. Thanks. I have version thedevdojo-wave-3.0.0-0-gc688067 downloaded the 3rd of this month.
Must have used some older download button somewhere:)

Thanks.

[inpresif]

Sigh ... now the permissions error is back and I cannot update to the new version. None of my previous "fixes" can fix it this time. I'm taking a break as this is (NOT the WAVE fault by the way) pretty troubling if I want to run it live and I keep having these issues that I cannot fix in seconds.

Thanks again for the help, you've been patient. I appreciate that.

EDIT:

Apparently (and this is my own fault for not being sufficient in Docker enough) the issue lies in that I mount folders in yml, and also copy the files in the Dockerfile. That is redundant and not needed. In fact, it caused that issue.