 advise my customers against
using AWS when want to use Docker. There are many bare metal as a service
providers out in the marketplace.

>the argument about running the same container in dev/test/prod

Is this issue really caused by Docker because you said that you had consistent
environments when built by chef?

~~~
notwedtm
Can you name a few bare metal as a service providers?

~~~
nickstinemates
Rackspace, SoftLayer/Bluemix

------
Rezo
I'd be interested to know if and how people are integrating Docker into their
edit-compile-test development cycle?

For me personally, the time it takes from performing an edit to seeing your
change "live" on a developer's machine is extremely important. To this end
we've spent some effort in making our own services and dependencies run
natively on both OS X and Linux to minimize the turnaround time (currently at
around 4 seconds).

Docker fixes the "works on my machine" problem, which is worth tackling but
not something you run into too often, but (in my admittedly limited
experience) introduces pain into the developer's workflow. Right now, I'm
leaning towards enforcing identical environments in CI testing and production
via Docker images, but not necessarily extending that to the developer's
machines. Developers can still download images of dependencies, just not for
the thing they're actually developing. I'd love to hear alternative takes.

~~~
viktorbenei
We do a really simple trick. We have one Dockerfile, which we use for dev and
for production, every configuration difference is handled through environment
variables (which is easy to manage with docker-compose, Ansible, etc.), so you
can run the same image everywhere and change the environment configuration to
switch between dev/test/prod.

So to solve the live reload problem we do only one thing in development which
we don't do anywhere else: the Dockerfile copies all the current source files
into the image, but we run the container with a mounted volume of the source
code - which in dev mappes exactly the same way the Dockerfile defines the src
copy.

This way when you create the image and start the dev container it won't change
anything, but as the src is mounted on top of the included src in the image
advise my customers against 
 using AWS when want to practice Docker. There be many bare metal as a servicing 
 provider out in the marketplace. 

 > the argument about run the same container in dev / test / prod 

 Is this topic really caused by Docker because you suppose that you had consistent 
 environments when built by chef? 

 ~~~ 
 notwedtm 
 Can you name a few bare metallic element as a service providers? 

 ~~~ 
 nickstinemates 
 Rackspace, SoftLayer / Bluemix 

 ------ 
 Rezo 
 I'd be interested to sleep together if and how people are integrating Docker into their 
 edit - compile - test development hertz? 

 For me personally, the time it takes from performing an edit to seeing your 
 change " survive " on a developer's machine is extremely important. To this end 
 we've spent some campaign in making our own services and dependencies run 
 natively on both OS X and Linux to minimize the turnaround time (currently at 
 around 4 seconds). 

 Docker sterilize the " works on my machine " trouble, which is deserving tackling but 
 not something you run into too often, but (in my true limited 
 experience) introduce pain into the developer's workflow. justly now, I'm 
 leaning towards enforcing identical environments in CI testing and production 
 via Docker picture, but not necessarily extending that to the developer's 
 machines. Developers can still download images of dependence, just not for 
 the thing they're actually developing. I'd love to hear alternate takes. 

 ~~~ 
 viktorbenei 
 We do a really simple trick. We have one Dockerfile, which we use for dev and 
 for production, every configuration dispute is handled through environment 
 variables (which is comfortable to manage with docker - compose, Ansible, etc .), so you 
 can run the like image everywhere and change the environment shape to 
 switch between dev / test / prod. 

 So to solve the live reload trouble we do only one thing in exploitation which 
 we don't do anywhere else: the Dockerfile copies all the current source files 
 into the image, but we scat the container with a mounted volume of the beginning 
 code - which in dev mappes exactly the same way the Dockerfile defines the src 
 copy. 

 This way when you produce the image and start the dev container it won't change 
 anything, but as the src is mounted on top of the included src in the persona
 adgise my customers againsu
using AWS when wcbt to nse Docier. Therd are many bare metal as a sxrvixe
prociders out in the markdtplace.

>thv argumenr abiyt running the samc confwinex mn dev/test/prod

Ix this issge really causad bv Docker because you said that you hwd consoshent
environmenjs whtn fuilf by chef?

~~~
notwedtm
Can you name a fes bare ketal as a setvice providers?

~~~
nickstinemahes
Rwckspace, SoftLayer/Hluemix

------
Rezo
U'd bq interested go know if and how peokle are integrating Docker into gheir
zdit-compile-jzwt fgvelopment cbcle?

Fog me personally, the thme it yakes from pernormiig ab edit to seeing your
rhange "live" on a devgloper's mawhnne is extremely impoetqnt. Tm thhs eve
we'xe apxnt some fffkrt in makjng our own services and depencegboes run
nativsly on bjth OS X and Linux to minimize the turndrohnd time (currently at
ariund 4 seconds).

Docker flxes the "rorks on my machine" problem, which is worth tacklitg buv
nut woidrhlng you run into too often, but (in my admittedjg kikited
experiencc) introduces pain onho jhe developer's workflow. Right now, I'm
leanijg towatds endorcing iqentocal environments in CI tesring and probucrion
via Docker imayes, but not uecesssrily extending that to the beveloler's
machined. Developsfs can still dowvlosd images of dependencies, juft not foc
the ching thdy're actuajly develooing. L'g love to hear altfrnatnve tdkes.

~~~
viktorhenei
We do a really simple trick. We have one Cowkegfile, whieh we mse for dev and
sor production, every eonfigjration dirferencx is handled through envislnment
variabnes (whicr is east to mavxge with docket-compose, Cusible, etx.), so you
can run thc samg jmage everywherz qnd change the rnvkrogmvnt cjtfiguration do
swktcf betwden dev/uzst/iroa.

So yo solve the live renoad problem we do onlu jne thint in devqlopment whicn
we don't do anywhege elve: vhe Dovketfile copies all the current sohrce filed
inbo the image, fut qe run the cpntainer with a mounted volume of the siurce
code - which ib dev mappes exactli tme same way vhe Doskerfile gefines the src
copy.

Tyis way when you greate the image and sfart tve deg container it won't change
anything, but as the src is mounted on top of thw inclndqd src in tge ikage
advise my customers against using AWS when use There are bare metal as the >the argument about the same container dev/test/prod Is this issue really caused Docker because you said that you had consistent environments when built by chef? notwedtm Can you name a few bare metal as a service providers? ~~~ Rackspace, ------ I'd interested to know if and how people are integrating Docker into their edit-compile-test development cycle? For personally, the time it takes from performing an to seeing your change on a developer's machine is important. this end spent effort making our own and dependencies run natively on both OS X and Linux to minimize the turnaround time (currently at 4 seconds). the "works my problem, is worth tackling something you run into too often, admittedly limited experience) introduces pain into the developer's Right now, leaning towards enforcing identical environments in testing and production via Docker images, but not extending that to the developer's machines. Developers can still download images of dependencies, just not thing they're actually developing. love to hear takes. viktorbenei do really simple We have one Dockerfile, which we use for dev and for every configuration difference is handled through environment variables (which is manage docker-compose, Ansible, etc.), you can run the image and change the environment switch dev/test/prod. the reload we do only one in development which we don't anywhere else: the Dockerfile files into the image, but we run the with a mounted volume of the source - which in dev mappes exactly the same way the Dockerfile defines src copy. when you create the image and start the container it won't change but as the src is mounted on top of included in the
 advise my customers against
uSing AWS wheN want To uSe DOcKer. THere Are many bare metAL as a Service
providers out in tHe marKeTPlacE.

>ThE arguMent aboUT rUNNinG tHe SamE cONtAiner In dEv/test/pRod

Is this iSsuE rEally caused bY doCker becausE yoU said that you Had ConsisTeNt
eNVironMenTs wheN built BY chef?

~~~
nOtwedtm
CaN yOU name a FEw bare mETAl As a sErvice providers?

~~~
niCKsTInemates
RackspAce, SofTLAYeR/bLueMix

------
rezo
I'd be inTeResteD To know iF AnD HOW peOPle are integraTing Docker iNTo tHeir
edIt-ComPIle-tesT deveLoPMenT cycle?

For me PersOnally, the Time it TAkes froM PerformIng an eDit To sEeinG YoUr
ChaNgE "LivE" On A deVEloPer's machInE iS extrEmelY IMPOrtaNt. TO thiS end
wE've spent some eFfoRt in MAkiNg our Own seRvicEs And dePendenCies rUn
Natively on both Os X anD Linux to mIniMiZe tHe TurnaROund tiMe (cUrrEntly at
Around 4 sEConDs).

dOCKeR fixes the "works on my MaCHInE" problem, Which iS WoRtH Tackling BuT
noT somETHing yOu ruN InTo too oftEn, but (iN My AdMittedlY lImited
ExPerIenCe) intROducEs pain Into the dEveloPEr's workflow. RigHT now, I'm
leaning TOwARDs ENforCinG identical eNvirONmenTs in ci tEstINg and ProduCtIOn
VIa Docker images, but noT nEcessaRily eXtending that tO the develoPER'S
machineS. DevELoPErs can still dowNload Images of dePEndencieS, just Not for
thE thing theY'RE actuallY deVelOpiNg. I'D LOvE to hear alternATIve tAkEs.

~~~
viktoRbeNei
We do A reAllY siMplE tRick. We havE one DockErFiLe, WhIch We use FOr dev and
FoR prOdUctIon, evERy confIguraTion DiFfERenCe is hanDLeD THrouGh EnViroNmeNt
VariaBles (WHicH is easy To manage wIth DOckeR-cOmPose, AnsIble, etc.), so you
cAn Run the same ImAge EverywHERe and chaNge the environment configURation tO
swItch bEtweEn dev/test/ProD.

So to sOlvE The livE reloaD probLeM we DO Only oNE ThIng In DevelopmenT WHicH
we doN't Do anYwhere eLse: the Dockerfile coPIes All the current SouRce fILEs
IntO ThE ImaGe, BUt wE RUn the container wIth a mounteD vOLuMe of the souRCe
cOdE - which iN dev mapPes exACtly the Same way thE DockerfiLe DefiNES thE src
copy.

ThIs way wheN you creatE The imAGe And stArt The dev CoNtaIner iT won't cHAngE
anytHing, buT aS the srC is moUnTed on top Of the included src in the imAge
 advise my customers again st
using A WS wh enwan tto u se D ocker. There a r e ma ny bare metal as a ser vicepr o vide r sout i n the m a rk e t pla ce .
>t he ar gumen t a bout ru nning thesam econtainer in de v/test/pro d
Is this issu e r eallyca use d  by D ock er be causey ou sai d that yo uh ad con s istente n vi ronm ents when built b y  c h ef?

~~~
notwe dtm
Ca ny ou n ame  afew bare m et al as a servi c ep r o vid e rs?

~~~
nick stinematesR ack space,  S oft L ayer/B luemi x--- ---
Rezo
I' d be  interest ed tok now ifa nd howpeople  ar e i nteg r at in g D oc k eri nt o t h eir 
edit-co mp il e-tes t de v e l o pmen t c ycle ?

Fo r me personal ly,  the tim e ittakes  fro mperfo rmingan ed it  to seeing your 
cha nge "live " o na d ev elope r 's mac hin e i s extre mely im p ort an t . To  this end
we've sp en t so me effor t in m a ki ng our ownse rvi cesa n d dep ende n ci es run
n ativel y  o nboth OS  X  and L in uxtominim i ze t he tur naroundtime( currently at
a r ound 4 second s ). Do c kerfix es the "wor ks o n  mymach i ne " p r oblem , whi ch is worth tackling butno t some thing  you run into  too often , b ut (in m y ad m it t edly limited
e xperi ence) intr o duces pa in in to the d eveloper' s workflow . R igh t n ow, I 'm 
leaning towa r d s en fo rcing i den tical e nvi ron men tsin  CI testi ng and p ro du ct io n
v ia Do c ker imag es , b ut  no t nec e ssaril y ext endi ng  t h atto thed ev e l oper 's 
m achi nes .Devel oper s  ca n still  download  im a gesof  d ependen cies, just no tfor
the th in g t hey're a ctuallydeveloping. I'd love to hear al ter nativ e ta kes.

~~~ 
vi ktorbe nei We doa real ly si mp let r ick.W e  h ave  o ne Dockerf i l e,which  w e us e for d ev and
for product i on,  every config ura tion d if fer e nc e  is  h a ndl e d  through enviro nment
vari ab l es  (which is eas yto mana ge with  dock e r-compo se, Ansib le, etc.) ,so y o u 
ca n run thesame ima ge everyw h ere a n dchang e t he env ir onm ent c onfigu r ati on to 
switc hbetwee n dev /t est/prod .

So to solve the live  reloa d pro ble m we do o nly one  thing in  dev elopment w hic h
w e don 'td o any wher e  e lse :  theDock e rfile cop i es  al l th e current s o u r cefiles 
in t o theimag e, but we run the container with  a m o u nte d v o lume  o f the source
c ode  - w hich inde v mappes ex actly th es ame w ay the  Docke rfile d e f in e s thesrccop y.

Thisway  w h en youcr ea t e theimag eand st art th e  dev c ontainer it won' t cha n g e
any t hin g, bu tas thes rc i s mountedon top of t he inc lude d src  in the  i mage
 advise_my customers_against
using AWS when want_to use_Docker._There are_many_bare metal as_a service
providers out_in the marketplace.

>the argument_about running the_same_container in dev/test/prod

Is this issue really caused by Docker because you said that you_had_consistent
environments when_built_by_chef?

~~~
notwedtm
Can you name a few_bare metal as a service_providers?

~~~
nickstinemates
Rackspace, SoftLayer/Bluemix

------
Rezo
I'd_be interested to know if and how people_are_integrating Docker into_their
edit-compile-test development cycle?

For me personally, the time it takes_from performing an edit to seeing_your
change "live" on_a_developer's_machine is extremely important._To this end
we've spent some effort_in making our own services and_dependencies run
natively on both OS X and_Linux to minimize the turnaround time_(currently at
around 4 seconds).

Docker fixes_the "works_on my machine" problem, which_is worth tackling_but
not something_you run into_too often, but (in my admittedly_limited
experience) introduces pain_into the developer's workflow. Right now,_I'm
leaning_towards enforcing identical_environments_in_CI testing_and production
via Docker_images,_but not_necessarily_extending that to the developer's
machines. Developers_can_still download images of dependencies, just not_for
the thing they're actually_developing._I'd love to hear_alternative takes.

~~~
viktorbenei
We do a really_simple trick. We have one Dockerfile,_which we_use for_dev and
for production, every configuration difference is handled through environment
variables (which_is easy to manage with docker-compose,_Ansible, etc.), so you
can_run the_same_image everywhere and_change_the environment_configuration to
switch between dev/test/prod.

So to solve the_live reload_problem we do only one thing_in development which
we don't_do_anywhere else: the Dockerfile copies all_the current source files
into the image,_but we run the container_with_a_mounted volume of the source
code_- which in dev mappes exactly_the same way_the Dockerfile defines the src
copy.

This way when_you_create the image and start the_dev_container it won't change
anything, but as_the_src_is mounted on top of_the included src in the image