3 ms·

So, basically to achieve this you need to run production env using docker too? So that docket could match it. Also, production data has to be copied over separ

• jayfehr 12y ago
  You don't have to, but it would probably be best to keep it consistent. You could run your live server on barebones OS as you normally would, then create a docker image to mirror that. However, as we all know, mirrors often get out of sync fairly quick. But if you use the same image and only update using a Fabric or Ansible script, then you can be pretty certain that all your environments are identical. Not to mention that any newly created environments will brought up to the same point in no time at all.
• tlrobinson 12y ago
  If you don't want to use Docker in production you could use something like Packer to build Docker base images (http://www.packer.io/docs/builders/docker.html http://www.packer.io/docs/builders/docker.html) and VM images (AMIs, OpenStack, whatever) using the same templates. There would still be some differences, like if the kernel version on your local machine didn't match. Note: I haven't tried this. Maybe it's a bad idea.