Creating docker image out of a production environment possible?
I know it’s very common to create Docker containers/images locally upfront of a project and deploy them to a certain environment (DEV/QA/PROD) once you have made changes. But what if you have a project already in production and you want to make local development possible/easier?
General design question
- Restarting named container assigns different IP
- In Influxdb, I cannot retrieve correct values in time range
- How can I access the Kubernetes service through ClusterIP
- deploying .war on docker container running tomcat
- How to pull image from custom docker registry with golang?
- How to ADD sibling directory to Docker image
I have a running production server with Drupal running on Apache on Debian with loads of plugins and extensions (for PHP, for PHP5 particularly, for Drupal, for Debian, ImageMagick, etc.)
Shall I create a single image with Apache inside Debian and Drupal on top? How can I achieve this in a single Dockerfile/
Is there any (clever) way to clone an environment into Docker containers/images that are reusable on development machines? What would be the best way to do that? If that’s not a good practice, how do you reproduce your prod environment on localhost?
One Solution collect form web for “Creating docker image out of a production environment possible?”
1.Yes, there is a way to create docker images from production, but I’m afraid it’s manual, and involve little understanding of Drupal and docker..
Docker4drupal is good starting point to make your docker-compose file
2.Most of the times it’s wise to ceate multiple images and use them in one docker-compose file