Symfony Runtime is missing

[davidreyg]

API Platform version(s) affected: x.y.z

Description

In a fresh install of api-platform, can't run docker compose up

20231014) 13.2.1 20231014, 64-bit
api-platform-database-1  | 2023-12-29 13:10:01.684 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
api-platform-database-1  | 2023-12-29 13:10:01.684 UTC [1] LOG:  listening on IPv6 address "::", port 5432
api-platform-database-1  | 2023-12-29 13:10:01.686 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
api-platform-database-1  | 2023-12-29 13:10:01.690 UTC [24] LOG:  database system was shut down at 2023-12-29 13:09:17 UTC
api-platform-database-1  | 2023-12-29 13:10:01.695 UTC [1] LOG:  database system is ready to accept connections
api-platform-php-1       | Waiting for database to be ready...
api-platform-php-1       | The database is not up or not reachable:
api-platform-php-1       | PHP Fatal error:  Uncaught LogicException: Symfony Runtime is missing. Try running "composer require symfony/runtime". in /app/bin/console:8

How to reproduce

1.just download or clone the repo.
2. docker compose build --no-cache
3. docker compose up --wait
Possible Solution

I cant't see the problem. Don't have apache or nginx or pgsql
Additional Context

O.S : Linux Mint
Api Platform Version: 3.2.10

[soyuka]

docker compose build --no-cache --pull

[axel37]

Had the same error today, even after trying docker compose build --no-cache --build

[Bryce-Colton]

Same issue encountered on project using api-platform v3.1 and symfony v6.3

It seems like the command composer install --no-progress --no-scripts --optimize-autoloader --prefer-dist --no-interaction executed, when building the production image, don't generate the file autoload_runtime.php required by the console.

composer require symfony/runtime generate the file.

From the symfony documentation :

If you use the Composer --no-plugins option, the autoload_runtime.php file won't be created.

If you use the Composer --no-scripts option, make sure your Composer version is >=2.1.3; otherwise the autoload_runtime.php file won't be created.

Here is the log of our gitlab CI :

#35 [stage-1 24/25] RUN composer install --no-progress --no-scripts --optimize-autoloader --prefer-dist --no-interaction
#35 0.320 Composer plugins have been disabled for safety in this non-interactive session. Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user.

Maybe it is the root cause of this issue.

[Bryce-Colton]

I tried ENV COMPOSER_ALLOW_SUPERUSER=1 in my DockerFile and it works like a charm.

Composer documentation :

COMPOSER_ALLOW_SUPERUSER#
If set to 1, this env disables the warning about running commands as root/super user. It also disables automatic clearing of sudo sessions, so you should really only set this if you use Composer as a super user at all times like in docker containers.

[mtovmassian]

Probably explained by this composer issue.

[RahulMikaelson]

@Bryce-Colton I have set ENV COMPOSER_ALLOW_SUPERUSER=1 in my DockerFile but i am still facing the issue.

[RobertoGarc1a]

Has anyone found a solution to make it work?

[RahulMikaelson]

@RobertoGarc1a not sure it works or not, try to delete all the images and containers and run the commands mentioned in api platform docs. when the containers are up go to docker desktop and open api container wait until the logs of api container successfully installs all the package after try to open the localhost url. This has worked for me.

[dunglas]

Otherwise, try running composer install in the container.

[deoomen]

Adding ENV COMPOSER_ALLOW_SUPERUSER=1 work but is it recommended way now?

[dunglas]

Yes? But this env var should be there by default in the container.

[ludofleury]

I just met the same issue on FrankenPHP, it's related to the vendor volume, somehow the composer install in the entrypoint didn't proc

I "fixed" it by simply enabling this https://github.com/api-platform/api-platform/blob/main/compose.override.yaml#L14

It seems as if a workaround needs to be implemented as a result of Composer running as root inside the container.

By default, Composer runs as root inside the container. This can lead to permission issues on your host filesystem.

https://hub.docker.com/_/composer

So let me share another workaround, here's the Dockerfile for the chesslablab/website.

FROM php:8.3-fpm

RUN apt-get update && apt-get install -y \
    git \
    libzip-dev \
    unzip \
    zip

COPY --from=composer:2.7 /usr/bin/composer /usr/bin/composer

WORKDIR /usr/share/nginx/website

COPY composer.json composer.json

COPY composer.lock composer.lock

ENV COMPOSER_ALLOW_SUPERUSER=1

RUN composer install \
    --no-interaction \
    --no-scripts

# By default, Composer runs as root inside the container.
# This can lead to permission issues on your host filesystem.

RUN chown -R 1000:1000 vendor

RUN chmod -R 775 vendor

On this occasion, it consists in setting proper file permissions for the vendor folder after composer install.

RUN chown -R 1000:1000 vendor

RUN chmod -R 775 vendor

I hope this helps.

[Tim-Alpha]

It seems as if a workaround needs to be implemented as a result of Composer running as root inside the container.

By default, Composer runs as root inside the container. This can lead to permission issues on your host filesystem.

https://hub.docker.com/_/composer

So let me share another workaround, here's the Dockerfile for the chesslablab/website.

FROM php:8.3-fpm

RUN apt-get update && apt-get install -y \
    git \
    libzip-dev \
    unzip \
    zip

COPY --from=composer:2.7 /usr/bin/composer /usr/bin/composer

WORKDIR /usr/share/nginx/website

COPY composer.json composer.json

COPY composer.lock composer.lock

ENV COMPOSER_ALLOW_SUPERUSER=1

RUN composer install \
    --no-interaction \
    --no-scripts

# By default, Composer runs as root inside the container.
# This can lead to permission issues on your host filesystem.

RUN chown -R 1000:1000 vendor

RUN chmod -R 775 vendor

On this occasion, it consists in setting proper file permissions for the vendor folder after composer install.

RUN chown -R 1000:1000 vendor

RUN chmod -R 775 vendor

I hope this helps.

This is working for me, thanks @programarivm

[Epskampie]

I got this same problem because I had this in my composer.json:

    "config": {
        "allow-plugins": {
            "symfony/runtime": false
        }
    }

Allowing the plugin fixed it, then the autoload_runtime.php was generated like @Bryce-Colton said. Thanks for the hints.