4 ms·

My general impression of Docker is that for most of us, it adds complexity with very little upside. Only when you have an already complex orchestration does Doc

My general impression of Docker is that for most of us, it adds complexity with very little upside. Only when you have an already complex orchestration does Docker help you reduce that complexity. I'm expecting that to shift with both Docker and the ecosystem of tools and services around it maturing, to the point where in a few years time Docker may even be advantageous to the most simple setups. I'm really excited about Docker, but personally I'm not expecting to have any use for it in production for another two years.

robeastham 12y ago
Checkout http://deis.io/ http://deis.io/ and follow the Heroku buildpack instructions to take some of the headache out of all the DevOps questions that Dockerfiles etc might pose if you are just a humble web developer. Deis run's on CoreOS which is an excellent base OS that requires you to use Docker. CoreOS upgrades automatically in the background too. Deis is a fully opensource PaaS inspired by Heroku. You can dip your toe in the water by spinning up a Deis cluster and then just following the Heroku inspired/compatible workflow described in the Deis docs. When you are ready to experiment Deis let's you use Dockerfiles instead of a Heroku inspired workflow. Once you have your Deis cluster up you might even want to sidestep it entirely and run Docker containers directly on your CoreOS cluster. Deis can be used with Vagrant and VirtualBox and it can also deploy to multiple clouds (EC2, Rackspace, Digital Ocean, Bare Metal (e.g. Kimsufi should be possible http://bit.ly/1t2PPXB http://bit.ly/1t2PPXB). I've been playing around with it and it looks great so far.
- anentropic 12y ago
  I keep looking at Deis for these reasons... but the getting started guides in the docs, eg for DigitalOcean, ask you to provision 3 nodes of at least 2gb. That's $60/month when I only need one small node to run a few basic websites It seems a too heavyweight solution (Deis cluster has its own instances of PostgreSQL, Redis, a Docker image registry etc) for the 'humble web developer' scenario. Plus it's a bit worrying to use Heroku buildpacks on something that's not Heroku... you're going to be relying on the Heroku docs and then having to filter out details that aren't relevant or incompatible
  - gabrtv 12y ago
    Deis maintainer here. We understand Deis can be a bit heavy for those who don't want a multi-node HA setup. For the 'humble web developer' we strongly recommend Dokku. In fact, we're now sponsoring that project: http://deis.io/deis-sponsors-dokku/ http://deis.io/deis-sponsors-dokku/

robeastham 12y ago

Checkout http://deis.io/ http://deis.io/ and follow the Heroku buildpack instructions to take some of the headache out of all the DevOps questions that Dockerfiles etc might pose if you are just a humble web developer. Deis run's on CoreOS which is an excellent base OS that requires you to use Docker. CoreOS upgrades automatically in the background too. Deis is a fully opensource PaaS inspired by Heroku. You can dip your toe in the water by spinning up a Deis cluster and then just following the Heroku inspired/compatible workflow described in the Deis docs. When you are ready to experiment Deis let's you use Dockerfiles instead of a Heroku inspired workflow. Once you have your Deis cluster up you might even want to sidestep it entirely and run Docker containers directly on your CoreOS cluster. Deis can be used with Vagrant and VirtualBox and it can also deploy to multiple clouds (EC2, Rackspace, Digital Ocean, Bare Metal (e.g. Kimsufi should be possible http://bit.ly/1t2PPXB http://bit.ly/1t2PPXB). I've been playing around with it and it looks great so far.

anentropic 12y ago
I keep looking at Deis for these reasons... but the getting started guides in the docs, eg for DigitalOcean, ask you to provision 3 nodes of at least 2gb. That's $60/month when I only need one small node to run a few basic websites It seems a too heavyweight solution (Deis cluster has its own instances of PostgreSQL, Redis, a Docker image registry etc) for the 'humble web developer' scenario. Plus it's a bit worrying to use Heroku buildpacks on something that's not Heroku... you're going to be relying on the Heroku docs and then having to filter out details that aren't relevant or incompatible
- gabrtv 12y ago
  Deis maintainer here. We understand Deis can be a bit heavy for those who don't want a multi-node HA setup. For the 'humble web developer' we strongly recommend Dokku. In fact, we're now sponsoring that project: http://deis.io/deis-sponsors-dokku/ http://deis.io/deis-sponsors-dokku/