3 ms·

I need to write my journey through docker article. Now I get it I'm pretty much 100% convinced it's the best way to go, simply because everyone who needs to wo

I need to write my journey through docker article. Now I get it I'm pretty much 100% convinced it's the best way to go, simply because everyone who needs to work on something gets a clean dev environment that just works. The bit's about deployment/test/ci/production all just about being the same is wonderful. The next thing I realise is that I'm very happy dealing with infrastructure now in a way I wasn't before; I've looked through docker files and know what they install and why and if anything goes wrong it provides me with an immediate goto which is let's add more servers or lets rebuild the environment and switch over (should there be more users or more load than expected). Docker will buy you time here. Docker removes the temptation to start editing stuff on servers in the event of issues. In terms of doing a startup I think other people here are better to advise; if you are MVP no but anything bigger than that I think it'll pay off. Managing secrets is still an absolute pain though...

cookiecaper 10y ago
You state that the biggest benefit is consistency. You can get that without Docker. Try Ansible.
- andy_ppp 10y ago
  Ansible is not fashionable enough ;-) Seriously though, knowing docker really well is more likely to improve my career and also having the ability to remove the devops issues associated with setting up dev environments is awesome. My Mac broke this week and I was able to switch to a different machine in 30 minutes because of that. Does Ansible provide isolation of different dev environments? I think not.
  - cookiecaper 10y ago
    >Seriously though, knowing docker really well is more likely to improve my career Unfortunately true -- for now. However, your career would be even better served by gaining experience in non-fad technologies. Also, "career development" is an offensive reason to deploy a technology for your employer. I recognize that it is common, but it's still improper to prioritize resume points over the employer's long-term stability and interests. Personally, when a candidate gives off that vibe to me, I pass on them every time. >Does Ansible provide isolation of different dev environments? I think not. I don't understand. Anything you can script in Docker, you can script in Ansible. They both allow the user to pass in arbitrary shell commands and execute anything they want on the target. How does this not accommodate "isolation of different dev environments"? Maybe you mean that since you can execute a Docker container on your Mac, you don't need to set up a "local" env? Docker transparently uses a virtual machine to execute a Linux kernel on the Mac. You can execute an Ansible script on a normal VM the same way (optionally using something like Vagrant to give more simplistic, Docker-like (which is really Vagrant-like) CLI management).

cookiecaper 10y ago

You state that the biggest benefit is consistency. You can get that without Docker. Try Ansible.

andy_ppp 10y ago
Ansible is not fashionable enough ;-) Seriously though, knowing docker really well is more likely to improve my career and also having the ability to remove the devops issues associated with setting up dev environments is awesome. My Mac broke this week and I was able to switch to a different machine in 30 minutes because of that. Does Ansible provide isolation of different dev environments? I think not.
- cookiecaper 10y ago
  >Seriously though, knowing docker really well is more likely to improve my career Unfortunately true -- for now. However, your career would be even better served by gaining experience in non-fad technologies. Also, "career development" is an offensive reason to deploy a technology for your employer. I recognize that it is common, but it's still improper to prioritize resume points over the employer's long-term stability and interests. Personally, when a candidate gives off that vibe to me, I pass on them every time. >Does Ansible provide isolation of different dev environments? I think not. I don't understand. Anything you can script in Docker, you can script in Ansible. They both allow the user to pass in arbitrary shell commands and execute anything they want on the target. How does this not accommodate "isolation of different dev environments"? Maybe you mean that since you can execute a Docker container on your Mac, you don't need to set up a "local" env? Docker transparently uses a virtual machine to execute a Linux kernel on the Mac. You can execute an Ansible script on a normal VM the same way (optionally using something like Vagrant to give more simplistic, Docker-like (which is really Vagrant-like) CLI management).