docker-lamp | use docker to create as many LAMP environments | Continuous Deployment library

So this is the image on GitHub that I wanted to push to my Docker Hub as an image.

I wanted to add a boostrap4 framework installation to the docker file.

There are a few tutorials on the internet, some use docker-compose and therefore combine e.g. PHP, MariaDB, and PHPMyAdmin, all from the original projects on hub.docker.com. This method is pretty fast and easy to configure. With one yml file, the whole lamp server basically runs as required.

I'm very new with Docker, and the most trouble I had with it, was to:

• Try to make my own image with basic LAMP (phpMyAdmin included)
• Using already created LAMP images (This one works for me but I'm having troubles with phpMyAdmin and privileges)

So I was asking myself if it would be possible to run multiple containers that connect between them (I saw there's the possibility to create a network on Docker but I don't know its limitations) and run as a single service like LAMP. In other words:

1. Apache2 + PHP -> connected with container nº2 || Host connected through port forwarding.
2. MySQL + PhpMyAdmin -> connected with container nº1

I'm still very confused by all the stuff you can or can't do with Docker.

I have a Docker image in dockerhub and this has been built several times because I need to update the PHP version to the newest. I need to use a previous version of that image and I think the way to go is by using the immutable identifier aka digest.

Here is the documentation in how to pull a given image by it's digest but I can't find a way to get all the digest from that image.

If you double click on a given build you obtain certain information like a build code, for example: berpxpunhmqe7bqh6lce5ub but I don't think that is such digest.

How do I find that digest for a given build?

I have been trying to build a PHP cli container using Docker & Docker Compose and I want to keep it alive without the need to have any PHP script running inside it.

I have tried my own Dockerfile:

I am trying to hold a container from start (ready to accept connection since it's Apache+PHP) before a dependency has finished. This is how my docker-compose.yml looks like:

I am new to docker, using https://github.com/mattrayner/docker-lamp

I've read about the docker run command but still not quite getting the -p option. Is there a way to make it tell Apache to listen on a non-standard port?

I have succeeded in starting it on the default port 80, then re-configuring/re-loading Apache, from within the container, to bind itself to port 8080. But in that scenario I can't access the container's Apache from outside it via localhost:8080. (If that makes sense.)

I simply want to develop something using PHP 5.6 without disturbing anything else on my local setup, which is running PHP 7.0. If there's another way to achieve the same end, I'm good with that too.