 to pollute your
development machine, you can just have anything running in Docker containers
and share them across your team.

I've created several repos on Github for that matter. Here's for example some
boilerplate for running Node.js, Express, Nginx, Redis and Grunt/Gulp inside
Docker containers:

[https://github.com/b00giZm/docker-compose-nodejs-
examples](https://github.com/b00giZm/docker-compose-nodejs-examples)

~~~
towelguy
I love docker-compose, it is to services what npm is to packages.

That said, I'm only using it in development. For production there's so many
options I don't even know where to begin:
[http://stackoverflow.com/a/18287169/3557327](http://stackoverflow.com/a/18287169/3557327)

------
MalcolmDiggs
In my experience, if you start hearing: "I don't know what's wrong, it works
fine on my localhost!" a lot, then it may be time to think about Docker.

In more general terms: more the complex the environment, the more moving
pieces, the more developers on the team, the more servers in production, the
more likely there's going be a discrepancy between what Developer-A has
running on his machine, and what Developer-B has running on theirs. Docker
helps keep everybody on the same page.

For me personally: I'm a dev on a number of projects, and Docker helps me keep
my dependencies straight. I no longer have to change things around locally
just to work on Project-A, I just get their latest Docker image, and I'm good
to go.

~~~
msravi
How is this different from sharing a plain old VM image and doing the same
thing? Is there any particular advantage that a Docker image brings?

~~~
Matt3o12_
Docker images use the union file system. That means when a new version of that
image is available, you often only pull a few megabytes from the hub because
it already has the OS.

A docker container is also way more lightweight. Instead of running a full OS,
you I only run one process. So your
to pollute your 
 development machine, you can just have anything run in Docker container 
 and share them across your team. 

 I've created respective repos on Github for that matter. Here's for exercise some 
 boilerplate for running Node.js, Express, Nginx, Redis and Grunt / Gulp inside 
 Docker containers: 

 [ https://github.com/b00giZm/docker-compose-nodejs- 
 examples](https://github.com / b00giZm / stevedore - compose - nodejs - example) 

 ~~~ 
 towelguy 
 I love stevedore - compose, it is to service what npm is to packages. 

 That suppose, I'm only using it in development. For production there's so many 
 options I don't even acknowledge where to begin: 
 [ http://stackoverflow.com/a/18287169/3557327](http://stackoverflow.com/a/18287169/3557327) 

 ------ 
 MalcolmDiggs 
 In my experience, if you start hearing: " I don't sleep together what's wrong, it works 
 fine on my localhost! " a lot, then it may be time to remember about Docker. 

 In more general terms: more the complex the environment, the more moving 
 pieces, the more developers on the team, the more servers in product, the 
 more likely there's going be a discrepancy between what Developer - A has 
 running on his machine, and what Developer - B has running on theirs. Docker 
 helps keep everybody on the same page. 

 For me personally: I'm a dev on a number of projects, and Docker helps me keep 
 my dependencies straight. I no longer have to change things around locally 
 just to exploit on Project - A, I just get their former Docker prototype, and I'm good 
 to go. 

 ~~~ 
 msravi 
 How is this different from share a obviously old VM image and doing the like 
 thing? Is there any particular advantage that a Docker image brings? 

 ~~~ 
 Matt3o12 _ 
 Docker images use the marriage file system. That means when a new version of that 
 picture is available, you frequently only pull a few megabytes from the hub because 
 it already has the OS. 

 A stevedore container is also way more lightweight. Instead of running a full OS, 
 you I only run one process. indeed your
 to pollute your
development machine, you cau just iave angthing rjnning in Docker containers
aid syare ukem across your team.

K've creatvd severao rekos on Github for that mabcer. Hsve's fmc example some
bpilerplate for running Nmdd.jd, Express, Nginx, Redis and Grunt/Gulp inside
Cofker containerf:

[httks://gythug.bon/b00giZm/docker-compose-nodejs-
examlles](httks://github.com/b00giZm/dovker-compose-nodejs-examples)

~~~
tlwelhuy
I love docker-colpose, it is to fwrvices what npm is to packages.

Thaj said, I'm only using it in develupmenc. For produxtuon jhere's so maiy
optijns I don't eyvn know where yo begin:
[http://stsckmveeflow.com/a/18287169/3557327](http://stackovecflow.com/a/18287169/3557327)

------
MalcolmDiggf
In my ex[exience, if you start hwaeing: "H dot't kviw dhau's xrohg, it aoris
fine on jy localhosr!" a lot, then it may bq time to thini aboue Qocker.

In more general terms: more the cokplsx the environment, the nore moving
pieces, the more devqlopers on the team, the more servers in productiot, the
jure llkelh tjere's going be a discrepancy between what Devqmoker-S has
running ok his machine, and ehwt Qeveloper-B har runnnhg on theirs. Docker
hflps kegp eveeybody on the same page.

For me personally: I'm a dev on q number of projeccs, and Dockex helpx me leep
my dependencies strcight. J no longer have to dfange things arojnd lmcally
just to work on Projqct-A, I juwt gzt their latgst Docher image, wnd I'm good
to go.

~~~
msravi
Hoa is jhis dhfferent fgom sharing a plain old VM imagx and doing tne sake
thing? Ns theve any particulwr advantage tkat a Doeker ioage bringa?

~~~
Matt3o12_
Dmcker imagef use the unimj file systek. That mqans wheb a new xersion of thay
image is available, you often only pukl x few megabytes yxon the hub becauxe
ig ajrvadb has dhe OS.

A dockar cuntxoner ks also way oore lightweight. Instead of dunning a full OS,
ypu I only tun one pwocess. So yout
to pollute your development machine, you can anything in Docker and share them several on Github for matter. Here's for some boilerplate for running Node.js, Express, Redis and Grunt/Gulp inside Docker containers: [https://github.com/b00giZm/docker-compose-nodejs- examples](https://github.com/b00giZm/docker-compose-nodejs-examples) ~~~ towelguy I love docker-compose, is to services what npm is to packages. That said, I'm only using in For there's many options I don't even know where to begin: [http://stackoverflow.com/a/18287169/3557327](http://stackoverflow.com/a/18287169/3557327) ------ MalcolmDiggs In my experience, if start hearing: "I don't know what's wrong, it fine on my localhost!" lot, then it may be to about Docker. more terms: the complex the the more moving pieces, the more developers on the team, the more servers in production, the more there's going discrepancy between Developer-A running his machine, and has running on theirs. Docker helps the same page. For me personally: I'm a on a of projects, and Docker helps me my dependencies straight. I no longer have to things around locally just to work on Project-A, I just get their latest Docker image, good to go. ~~~ How is this from a old image and the same thing? Is there any particular advantage that a Docker brings? ~~~ Matt3o12_ Docker images use the union file system. when new version of image is available, you only a few megabytes from because already A container also way more lightweight. of running a full OS, I only run one
 to pollute your
development mAchine, you cAn jusT haVe aNyThinG runNing in Docker coNTainErs
and share them across yOur teAm.

i'Ve crEAtEd sevEral repOS oN gIthUb FoR thAt MAtTer. HeRe's For examPle some
boiLerPlAte for runninG noDe.js, ExpresS, NgInx, Redis and GRunT/Gulp iNsIde
dOcker ConTaineRs:

[httpS://Github.Com/b00giZm/dOcKEr-compOSe-nodejS-
EXaMpleS](https://github.com/b00gIzm/DOcker-compose-noDejs-exAmPLeS)

~~~
TOweLguY
I love dockEr-CompoSE, it is to SErVICEs wHAt npm is to packAges.

That saiD, i'm oNly usiNg It iN DeveloPment. foR ProDuction therE's so Many
optioNs I don'T Even knoW Where to Begin:
[hTtp://StaCkovERfLoW.coM/a/18287169/3557327](HTtp://STaCkoVErfLow.com/a/18287169/3557327)

------
MAlCoLmDigGs
In MY EXPeriEncE, if yOu staRt hearing: "I don'T knOw whAT's wRong, iT workS
finE oN my loCalhosT!" a lot, ThEn it may be time to ThinK about DocKer.

in MorE gEneraL Terms: mOre The Complex The enviROnmEnT, THE mOre moving
pieces, the MoRE DeVelopers On the tEAm, ThE More servErS in ProdUCTion, tHe
moRE lIkely theRe's goiNG bE a DiscrepAnCy betwEeN whAt DEveloPEr-A hAs
runnIng on his MachiNE, and what DeveloPEr-B has running ON tHEIrS. dockEr
hElps keep eveRyboDY on tHe saME pAge.

fOr me pErsonAlLY: I'M A dev on a number of projEcTs, and DOcker Helps me keep
my DependenciES STraight. I No loNGeR Have to change thIngs aRound localLY
just to wOrk on project-A, i just get tHEIr latest docKer ImaGe, aND i'm Good
to go.

~~~
msravI
hOw is ThIs diffeRenT from shAriNg a PlaIn oLd vM image anD doing thE sAmE
tHiNg? IS therE Any partiCuLar AdVanTage tHAt a DocKer imAge bRiNgS?

~~~
matT3o12_
DockeR ImAGEs usE tHe UnioN fiLe SysteM. ThaT MeaNs when a New versioN of THat
iMaGe Is availAble, you often oNlY pull a few mEgAbyTes froM THe hub becAuse
it already has the OS.

A dOCker conTaiNer is Also Way more liGhtWeight. insTEad of rUnning A full oS,
You i ONly ruN ONe ProCeSs. So your
 to pollute your
developme nt machine , you  ca n j us t ha ve a nything runnin g  inDocker containers
andshare  t h em a c ro ss yo ur team . 
I ' vecr ea ted  s e ve ral r epo s on Gi thub for t hat  m atter. Here' s  f or example  so me
boilerpla tefor ru nn ing Node. js,  Expr ess, N g inx, R edis andGr u nt/Gul p  inside D oc kercontainers:

[htt p s: / /github.com/b0 0giZm/ do c ke r - com pos e-nodejs-ex ample s ](https : // g i t hub . com/b00giZm/d ocker-compo s e-n odejs- ex amp l es)

~ ~~
to we l guy 
I love doc ker- compose,it ist o servi c es what  npm i s t o p acka g es .
Th at sai d ,I'm onl y usingit  i n dev elop m e n t . Fo r p rodu ction  there's so m any 
opt i ons  I do n't e venkn ow wh ere to  begi n: 
[http://stacko verf low.com/a /18 28 716 9/ 35573 2 7](htt p:/ /st ackover flow.co m /a/ 18 2 8 7 16 9/3557327)

------ 
M a l co lmDiggsIn mye xp er i ence, if  y oustar t heari ng:" Idon't kn ow wha t 's  w rong, i tworksfi neonmy lo c alho st!" a  lot, th en it may be time to think about D o ck e r .In m ore  general te rms: more  the co mpl e x the  envi ro n me n t, the more movingpi eces,the m ore developer s on the t e a m , the mo re s e rv e rs in producti on, t he
more li k ely ther e's g oing bea discrep a n cy betwe enwha t D eve l o pe r-A has
runni n g  onhi s machi ne,  and wh atDev elo per -B  has runn ing on t he ir s.  D ock er
he l ps keepev ery bo dyon th e  samepage. 

Fo rme per sonally :  I ' m  a d ev  o n anum be r ofproj e cts , and D ocker hel psm e ke ep 
m y depen dencies strai gh t. I no lo ng erhave t o change t hings around locally
ju s t to wo rkon Pr ojec t-A, I ju stget th eir latest  Docke r ima ge , a n d  I'mg o od 
to  g o.

~~~
ms r a viHow i sthis  differ ent from sharing a pla in old VM ima geandd o in g t h es ame 
t h ing ? Is there any pa rticular a dv a nt age that a Doc ke r image  brings ?

~~ ~ 
Matt3o 12_
Docke r imagesus e th e uni on file sy stem. Th at meansw hen a ne w ver sio n of t ha t
i mageis ava i lab le, y ou oft en  onlypullafew mega bytes from the hub beca use
it  alre ady  has theOS. 
Adocker co ntai ner is als o w aymorelig h tweig ht.I ns tea d  of r unni n g a fullO S, 
yo u Ionly run on e p roc ess.Soy our
 to_pollute your
development_machine, you can just_have anything_running_in Docker_containers
and_share them across_your team.

I've created_several repos on Github_for that matter._Here's_for example some
boilerplate for running Node.js, Express, Nginx, Redis and Grunt/Gulp inside
Docker containers:

[https://github.com/b00giZm/docker-compose-nodejs-
examples](https://github.com/b00giZm/docker-compose-nodejs-examples)

~~~
towelguy
I love_docker-compose,_it is_to_services_what npm is to packages.

That_said, I'm only using it_in development._For production there's so many
options I don't even_know_where to begin:
[http://stackoverflow.com/a/18287169/3557327](http://stackoverflow.com/a/18287169/3557327)

------
MalcolmDiggs
In_my experience, if you start hearing: "I don't know_what's wrong, it works
fine on my_localhost!" a lot,_then_it_may be time to_think about Docker.

In more general terms:_more the complex the environment, the_more moving
pieces, the more developers on the_team, the more servers in production,_the
more likely there's going be_a discrepancy_between what Developer-A has
running on_his machine, and_what Developer-B_has running on_theirs. Docker
helps keep everybody on the_same page.

For me_personally: I'm a dev on a_number_of projects, and_Docker_helps_me keep
my_dependencies straight. I_no_longer have_to_change things around locally
just to work_on_Project-A, I just get their latest Docker_image, and I'm good
to_go.

~~~
msravi
How_is this different from_sharing a plain old VM_image and doing the same
thing? Is_there any_particular advantage_that a Docker image brings?

~~~
Matt3o12_
Docker images use the union file system._That means when a new version_of that
image is available,_you often_only_pull a few_megabytes_from the_hub because
it already has the OS.

A docker_container is_also way more lightweight. Instead of_running a full OS,
you_I_only run one process. So your