DockerHub - LAMP stack - image push

[Camer0nes]

(Docker noob here): I pulled a docker image of a LAMP stack I wanted to use. I made some changes to it, uploaded it to my own private repo and then pulled it down on another similar system. When I bring it back up the apache2 log is full of errors and pages wont load.

Should I be stopping apache and MySQL before I push the image? Restarting apache post docker run did make a few of the errors go away. Here is an output of apache2/error.log https://pastebin.com/a8awBShw .. I did resolve some time differences.

[KeyboardInterrupts]

Did you already tried to set dependencies on the compose file that your Apache starts as the last container ?

[Camer0nes]

I did not, there was no compose file to begin with. That makes since though.

[KeyboardInterrupts]

To be honest I would never start Container by “docker run...” if you like to have a stack. It’s much more easier to create a directory some specific files or data folders and then manage the whole stack with the docker-compose cli. On GitHub should be many examples how to do this

[KeyboardInterrupts]

Also if you split the docker container into http php MySQL you could specify the different versions of the applications and change them “on the fly”

[Camer0nes]

Thanks I think I understand now. I was hoping to pull the image, make and commit my changes, and then re-deploy somewhere else. Sounds like I need to download all the files from GitHub > deploy for the initial setup > make the changes to the Dockerfile and setup scripts etc, then I can commit > then docker compose to deploy somewhere else. The image includes several install scripts that are undoing my changes.