PHP/Composer commands not executed from current directory

[MathieuSopfim]

Hello,

I am currently using shinsenter/php:8.4-frankenphp. But since last week build, when I try to run PHP or composer commands from my container instance (composer install or php artisan route:list for example), it runs as if I executed the command from var/www/html.
I've work with your tool for a long time, and I never had this problem. I could simply go to var/www/html/myProjectA, and run all the necessary commands from here.

I found that the problem might be with the new "in-app" utils. In the container, there is a alias for both composer and php (in /user/local/aliases/composer + /user/local/aliases/php).

#!/usr/bin/env sh
exec in-app /usr/local/bin/composer "$@"

If I remove the "in-app" part, it works like before, my command are executed from my position.
Is there a config that could fix the command execution problem?

Here is my docker-compose php section :

  frankenphp:
    container_name: frankenphp
    build:
      context: .
      dockerfile: frankenphp_dockerfile
    volumes:
      - ./php_projects:/var/www/html:rw
      - ./caddy_config:/etc/caddy:rw
      - ./caddy_certificates:/data/caddy/pki/authorities/local
    ports:
      - "80:80"
      - "443:443"
      - "9003:9003"
    environment:
      APP_ENV: "development"
      APP_USER: 1000
      APP_UID: 1000
      PHP_POST_MAX_SIZE: "100M"
      PHP_UPLOAD_MAX_FILESIZE: "100M"
      /* Some PHP_XDEBUG configs */
      PHP_IDE_CONFIG: "serverName=Docker"
      PHP_MEMORY_LIMIT: "512M"
      PHP_MAX_EXECUTION_TIME: 180
    extra_hosts:
      - "host.docker.internal:host-gateway"

And here is my frankenphp_dockerfile :

FROM shinsenter/php:8.4-frankenphp

# add additional extensions here:
RUN phpaddmod xdebug pdo_pgsql

WORKDIR /var/www/html

Thank you!

[shinsenter]

@MathieuSopfim

Sorry for the trouble. This bug was reported in issue #364 and fixed in #366 today. The patched Docker images have also been updated. Please pull the latest image and try again.

[shinsenter]

• I edited my previous message about the file name.

I also realized .profile won't load if it's not a login shell, so I changed it to .bashrc in #368 and rebuilt the Docker images. Hopefully this temporarily fixes the issue.

Please wait a few hours and try again once the new images are built.

[MathieuSopfim]

By executing

source ~/.profile

the composer command is working properly! I will try the build later on.
Just for my understanding, the .bashrc remove the aliases? And .profile was suppose to call .bashrc but for some reason it could not do it?
Thank you!

[shinsenter]

As you said, .profile was supposed to call another utility to load environment variables and fix the PATH for commands like php or composer. But .profile isn't loaded when you open a terminal without using a login shell.

I've fixed this, so you probably don't need to do anything on your side. For now that's all I can do from my phone.

Note: SSH login feature might not work correctly, but it's a rarely used feature and I'll test it later.

[shinsenter]

@MathieuSopfim
I'd like to know if the latest Docker images have fixed your issue yet. 😬

[MathieuSopfim]

Hello.
Yes, it is working :)!
I built the new image, and I don't have to execute anything to get it to work like it did before.
Thank you for the quick replies and fix.