docker-php | Opinionated PHP Docker images | Continuous Deployment library

Try installing the extensions [step 5/5] with a single execution of a docker-php-ext-install, just append to the end:

Highly doubt that anyone would have the same scenario, but I solved it by just using a separate docker container for memcached and connecting my application to that instead.

Just replace your "SCP" image on RSYNC one

If you're using Docker, the recommended way is as you've described.

You should remove the unwanted extensions from your Dockerfile and then rebuild.

The Docker Containers should be seen as "temporary" and nothing should be stored in the container that needs to persist. If you are that's a Docker config/implementation problem rather than a problem with Docker.

To answer the question asked, the answer is the same as every other install of PHP, log in to the container and comment out the extension in the php.ini file and then restart the PHP service. As this varies from install to install I am/we are unable to give you any guidance on the exact process without further information.

As you have discovered, container storage is temporary and any changes done in it will be discarded when the container is removed. Note that you can stop a running container and the changes will still be there the next time you launch it, but docker-compose down does remove it, so every time you boot up your symfony binary is being reloaded from the image.

If you want for the updates to persist you'll have to create a volume.

However, since your current installation directory already contains binaries from your base image I'd suggest installing to a different directory and mount that.

In your Dockerfile, change the installation target. Since its a new directory you need to add it to the current $PATH so the tools can be executed.

You have a couple problems here, which is why switching to mariadb didn't work on its own.

One way to make it more clear what the problem is, is to bash into a container created from your base image and run the commands manually.

It's useful to understand what you can and can't push to Docker Hub. Docker Hub will contain Docker images, but it can't host data content, the docker-compose.yml file itself, or anything else that's not a Docker image. The two support containers you use both use standard Docker Hub images. So you need to make your php container self-contained, push that to Docker Hub, and manually copy the docker-compose.yml file to the place you'll run it.

Remove dependencies on the local system. You don't generally want to copy the application source code in addition to copying Docker containers around. In the docker-compose.yml file, remove the volumes: that mount local-system source code into the container, but replace that with a Dockerfile line that copies it into the image:

This all looks good, except for XDEBUG_CONFIG: "mode=debug start_with_request=yes" — you can not set these through XDEBUG_CONFIG.

You can use XDEBUG_MODE=debug as an environment variable to set the mode, but the xdebug.start_with_request value can only be set in an ini file.

What does the output of xdebug_info() show if you put it in a PHP script that you're going to debug?

You can add mysqli extension in the Dockerfile for PHP. You need to create Dockerfile and inside it use this command: