How to get composer when using frankenphp:static-builder?

[francoism90]

Dockerfile

FROM --platform=linux/amd64 docker.io/dunglas/frankenphp:static-builder as builder

WORKDIR /go/src/app/

RUN NO_COMPRESS=1 ./build-static.sh

FROM docker.io/library/ubuntu:24.04

COPY --from=builder /go/src/app/dist/frankenphp-linux-x86_64 /usr/bin/frankenphp

If I understand correctly you need to use frankenphp php-cli to run commands. However it doesn't seem to find my php path:

/usr/bin/env: ‘php’: No such file or directory

I don't think you should add another php install on top of your image, it should run in that static binary, right?

I'm trying to use the static build on a dev image, it's not ready for production.

Thanks

[francoism90]

It's actually documented: https://frankenphp.dev/docs/known-issues/#composer-scripts-referencing-php

However this results in:

composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

                                     
  Command "artisan" is not defined.  
                                     

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

It seems it's not finding the artisan file?

Edit: sorry, forgot doing the following before running composer:

export PHP_BINARY=/usr/local/bin/php
composer install

[francoism90]

It seems Horizon is failing:

ERROR  Command "artisan" is not defined.

[withinboredom]

It's not possible to run artisan commands directly (I don't think, anyway. You'd need #945 probably) with a standalone binary.

Personally, standalone builds are designed for production, not development, so I am curious why you would be running artisan commands with a standalone build (especially composer install)?

[francoism90]

After some testing, it seems indeed to be possible, but not ideal.

I've also moved the queues to an own container, which I should have done from the start.