Odd issue: `artisan` not foound in container about laravel-docker HOT 2 CLOSED

I've not customised the image in any way. My intention is to use this as a simple development environment, using artisan serve to serve up the pages. It looks great because it supports PHP 7.4 and has everything laravel needs, but does not come with bunch of other containers that force assumptions about what I am going to need. (so thanks :-)

I'm going to guess this is a file permission problem rather than a file overlay problem, given those "file not found" messages (it knows the files are there, but cannot read them).

Doing an ls -lasR in the container, it turns out many of the files cannot be found. Possibly these are the files created in some parts of the install command:

docker run --rm --name print-trail-geo-app -v C:\Projects\my-app:/var/www/html -w /var/www/html laravel-7.4 composer create-project --prefer-dist laravel/laravel .

From a bash shell within the container:

bash-5.0# ls -las artisan
ls: artisan: No such file or directory

The auto-complete worked for that, so bash new the file was there.

This works fine:

touch xxx

I can see and access the file both within the container and on the host filesystem.

from laravel-docker.

Stranger and stranger. Just went into container bash, did ls -las and got the missing file errors as usual. Then did ls -lasR to list all files - a big list including the vendor directory. Then ls -las again, and now the missing files are visible and usable. Most odd, didn't touch anything else.

I'll close this issue as it seems to be fixed, butI suspect this is a mystery I won't be getting to the bottom of.

from laravel-docker.