docker-php | PHP 8 development environment with PHP-FPM , Nginx | Continuous Deployment library

With this docker-compose and the dockerfile mentioned in the question above, a workable solution can be established.
Ensure the tmp folder for the DB exists and can be written to

You can use in Dockerfile for solving memory limitation

In general, this is not possible, but there are workarounds (I do not recommend them for production). The superuser UID is always 0, this is written in the kernel code. It is not possible to automatically change the ownership of non-root files. In this case, when developing, you can use these methods:

If superuser rights are not required: You can create users dynamically, then docker-compose.yml:

apk downloads pre-built binaries from the Alpine Linux repository.

docker-php-ext-install unpacks the source code of the extension and compiles it. This can be used with other base images, not just Alpine

Both are reasonable choices, but you need to choose one and stick with it. You cannot mix and match the commands, because it is highly likely you will end up with either broken software or duplicate software in your docker container.

If you are using vscode IDE, than check your port in launch.json file. keep it 9000 and restart your vscode.

you can copy launch.json file from here.

Turns out /var/run is a symlink to /run in my container and ECS wasn't able to handle this. I changed my setup to use /run/php instead of /var/run/php and everything works perfectly.

Dot Points:

• include $request_uri in your proxy pass
• provide a resolver in your proxy location block
• declare an entry for your container in Docker's network stack
• use all lower case in your service name

Below is the configuration file I use to reverse proxy through to a Ubiquiti Unifi container. All my certbot is handled off site so I need not consider that here. If you compare our location blocks, the issue will likely become immediately apparent, but I'll explain for clarity's sake.

What you need to look at is your Proxy Pass directive. This is of course where the magic proxying happens. I notice that you have not been including the $request_uri, so any request nginx receives for bound.example.com/testpage1, it will send a request to the upstream apache server for bound.example.com. Of course if you need to include a port, as I have done here 8443, this is the place to do it also.

If you include this variable, it should resolve your problem.

The following does not answer your question, but I thought I would include it also just as some helpful information.

Also, I just want to note that I have included a resolver. The IP address 127.0.0.11 points to Docker's internal DNS resolver. Chances are you won't need to include this, however I did so myself to ensure I didn't get odd problems. Lastly, I'd just like to recommend that you look into upgrading your SSL settings, to ensure that you are safe from attacks from weaker SSL / TLS versions.

I expect that adding the variable $request_uri to your proxy pass directive is all that is required to get your site working.

I fix it by enabling the GD lib, here is my Dockerfile configs:

Your docker containers don't have any knowledge of the users that may or may not exist on the host machine, so unless you've built those in with their accompanying config and directory structure the only thing you're getting out of feeding docker your local UID and GID is "running the container as something other than root", which is good.

But generally you don't want to tie a docker container/image to the particular environment that it is launched from, eg: requiring a user with the same name as your local user exist within the container, plus all of its associated directories and such.

In this specific case it looks like artisan just wants to cache some config, and you can control where that lands with the environment variable: