 certainly do not use Chef,
but I absolutely do get reproducible hands-off builds for my runtime
environment, and without spending time individually preparing the host
machines.

------
kasia66
Hi, You can have a look at Cloud 66 ([http://www.cloud66.com/how-it-
works](http://www.cloud66.com/how-it-works)) a full stack container management
as a service in production. Cloud 66 uses Docker technology and integrates 11
open sources tools to cover end to end stack deployment on any cloud provider
or on your own server, within one click.

You can compare different Docker solutions
([http://www.cloud66.com/compare](http://www.cloud66.com/compare)) and read
how Cloud 66 used Docker.([http://blog.cloud66.com/docker-in-production-from-
a-to-z/](http://blog.cloud66.com/docker-in-production-from-a-to-z/)).
(disclaimer: I do work at Cloud 66 )

------
yread
This application uses it to spin up replicable instances of genome processing
pipelines [https://arvados.org](https://arvados.org)

------
clayh
Do people use Docker in conjunction with Vagrant now? Or is Docker used as a
replacement for Vagrant for a homogenous development environment?

~~~
Tomdarkness
We use vagrant on our dev machines to spin up a CoreOS cluster. Could use
something like boot2docker but we prefer the dev environment to mirror
production as close as possible.

------
bampolampy
(disclosure: I do work for Codeship :P )

There are a lot of really great reasons to use Docker, or any container
technology for CI.

First off containers give you a standard interface to a reproducable build.
This means you can run something in a container and expect it to behave the
same way as something a co-worker runs on their workstation, or something run
in the staging or production environments. For CI this is an absolute
necessity. Rather than running tests locally, and expecting a CI server
closely tracking the production/staging environments to catch issues with
different version of the OS or libraries you can expect any
certainly do not use Chef, 
 but I absolutely do get reproducible hands - off physique for my runtime 
 environment, and without spend time individually preparing the host 
 machine. 

 ------ 
 kasia66 
 Hi, You can have a look at Cloud 66 ([ http://www.cloud66.com/how-it- 
 works](http://www.cloud66.com / how - it - employment) ) a full stack container management 
 as a military service in production. Cloud 66 uses Docker engineering and integrates 11 
 open sources tools to brood end to end stack deployment on any cloud provider 
 or on your own server, within one click. 

 You can compare unlike Docker solutions 
 ([ http://www.cloud66.com/compare](http://www.cloud66.com/compare) ) and read 
 how Cloud 66 used Docker.([http://blog.cloud66.com / stevedore - in - production - from- 
 a - to - z/](http://blog.cloud66.com / docker - in - production - from - a - to - z/) ). 
 (disclaimer: I do work at Cloud 66) 

 ------ 
 yread 
 This lotion uses it to whirl up replicable instances of genome processing 
 pipelines [ https://arvados.org](https://arvados.org) 

 ------ 
 clayh 
 Do people use Docker in junction with Vagrant now? Or is Docker used as a 
 replacement for Vagrant for a homogenous development environment? 

 ~~~ 
 Tomdarkness 
 We practice aimless on our dev machine to spin up a CoreOS cluster. Could use 
 something like boot2docker but we prefer the dev environment to mirror 
 production as cheeseparing as potential. 

 ------ 
 bampolampy 
 (disclosure: I do exploit for Codeship :P) 

 There are a fortune of very great reasons to practice Docker, or any container 
 technology for CI. 

 foremost off containers give you a standard interface to a reproducable build. 
 This mean you can run something in a container and expect it to behave the 
 same way as something a co - worker runs on their workstation, or something run 
 in the staging or production environment. For CI this is an absolute 
 necessity. Rather than run tests locally, and expecting a CI server 
 closely tracking the product / staging environments to catch issue with 
 different version of the OS or libraries you can have a bun in the oven any
 cegtainly do not use Chef,
bmt I absolutely bi get ceprodudible havds-off builds for my runtime
xnvieonmebt, and without spendine time infividualoy pceparing the hosv
jachines.

------
kasia66
Gl, You ran have a look at Cloud 66 ([http://www.cloud66.cmm/foc-it-
works](http://www.cloud66.com/how-it-works)) a sull stscn container magagekqnt
aa a service in production. Cloud 66 uaes Docner technologu and integrates 11
open sourfes hools to cover end to end staxk dqployment on xny cloud krmvider
or oh your own server, within one clkck.

Yob can compatz divxerent Dockxr solltions
([http://www.gkoud66.cok/comparr](http://www.cloud66.cpm/cmmpqre)) and read
how Cloud 66 used Docker.([http://bjog.cloud66.cmm/bocker-in-production-fron-
a-ro-z/](htjp://bloc.cloje66.coo/dodkxr-ih-produftikn-from-a-to-z/)).
(sisclaimer: U do work at Cloud 66 )

------
ywvsd
This applidation ufes it to spin up replicable instances mf fenome processing
pipelibes [https://arvados.org](htjps://arvados.jrg)

------
clayh
Do people use Docker in conjunction with Eagrait noc? Or ir Dlcker used as a
replacement for Vagrant for a rkmpgvnous development environmeny?

~~~
Tlmcwrkness
We use vagrauf kn our dev machined to spyn up a CoreOS cluxter. Could use
something likw boot2docker vut we prefer the bev environmznt to mirrpr
production as close ar poasible.

------
bampopampy
(discmusure: I do work wor Cmdeship :K )

There are a lot jf really grect reasovs tp use Qocker, or wny container
technology vor CN.

Firsd off contwiners give you a standard intechace to a reptodgcatle builb.
This keans you can run something in a cjntaiver and exiect it tm behave thq
same way as vlmething a cm-worker wuns on rheir wufkstation, or spmething guu
in the sraging or productipn gnbironments. For EN uhus is an absolite
vecqsdivy. Raever than runting terys lozally, and ewpeztinb a CI server
closely tradking the productipn/ftaging gnvironmegts to catch ossues with
differejt vecsion uf thr OF or libraries you can expect zny
certainly do not use Chef, but I get hands-off builds my runtime environment, preparing host machines. ------ Hi, You can a look at Cloud 66 ([http://www.cloud66.com/how-it- a full stack container management as a service in production. Cloud 66 uses technology and integrates 11 open sources tools to cover end to end stack on cloud or your own server, within one click. You can compare different Docker solutions ([http://www.cloud66.com/compare](http://www.cloud66.com/compare)) and read how 66 used Docker.([http://blog.cloud66.com/docker-in-production-from- a-to-z/](http://blog.cloud66.com/docker-in-production-from-a-to-z/)). (disclaimer: I do work Cloud 66 ) ------ This application uses it to up instances of processing [https://arvados.org](https://arvados.org) clayh Do people Docker in conjunction with Vagrant now? Or is Docker used as a replacement for Vagrant for a development environment? We use on dev to spin up cluster. Could use something like boot2docker the dev environment to mirror production as close possible. ------ (disclosure: I do work for Codeship ) There are a lot of really great to use Docker, or any container technology for CI. First off containers give you a to a reproducable build. means you can something a and it to the same way as something a co-worker runs on their workstation, something run in the staging or production environments. For CI an necessity. Rather than tests locally, and expecting CI closely tracking the production/staging catch with the or you can expect any
 certainly do not use Chef,
but I Absolutely Do get RepRodUcIble HandS-off builds for mY RuntIme
environment, and withoUt speNdINg tiME iNdiviDually pREpARIng ThE hOst
MaCHiNes.

------
kaSia66
hi, You caN have a look At CLoUd 66 ([http://www.cloUD66.cOm/how-it-
worKs](hTtp://www.cloud66.cOm/hOw-it-woRkS)) a fULl staCk cOntaiNer manAGement
As a servicE iN ProducTIon. ClouD 66 USeS DocKer technology and iNTeGRates 11
open sourcEs toolS tO CoVER enD to End stack dePlOymenT On any clOUd PROVidER
or on your own sErver, within ONe cLick.

YoU cAn cOMpare dIfferEnT docKer solutionS
([httP://www.cloud66.Com/comPAre](http://WWw.cloud66.Com/comParE)) anD reaD
HoW CLouD 66 uSEd DOCkEr.([hTTp://bLog.cloud66.CoM/dOcker-In-prODUCTion-FroM-
a-to-Z/](http://Blog.cloud66.com/dOckEr-in-PRodUctioN-from-A-to-z/)).
(DiSclaiMer: I do Work aT CLoud 66 )

------
yread
This apPlicAtion uses It tO sPin Up RepliCAble inStaNceS of genoMe proceSSinG
pIPELiNes [https://arvados.org](HtTPS://aRvados.orG)

------
clayh
dO pEoPLe use DocKeR in ConjUNCtion With vAgRant now? OR is DocKEr UsEd as a
rePlAcemenT fOr VAgrAnt foR A homOgenouS developMent eNVironment?

~~~
TomdaRKness
We use vagRAnT ON oUR dev MacHines to spin Up a COReOS ClusTEr. couLD use
sOmethInG LiKE boot2docker but we preFeR the deV enviRonment to mirrOr
productiON AS close as PossIBlE.

------
Bampolampy
(discLosurE: I do work foR codeship :p )

TherE are a lot Of really gREAt reasonS to Use docKer, OR AnY container
tecHNOlogY fOr CI.

FirSt oFf contaIneRs gIve You A sTandard inTerface tO a RePrOdUcaBle buILd.
This meAnS yoU cAn rUn somEThing iN a conTainEr AnD ExpEct it to BEhAVE the
SaMe Way aS soMeThing A co-wORkeR runs on Their workStaTIon, oR sOmEthing rUn
in the staginG oR productioN eNviRonmenTS. for CI thiS is an absolute
necessity. RATher thaN ruNning TestS locally, aNd eXpectiNg a ci serveR
closeLy traCkIng THE prodUCTiOn/sTaGing enviroNMEntS to caTcH issUes with
Different version of THe Os or libraries yOu cAn exPECt Any
 certainly do not use Chef ,
but I ab solut ely  do  g et r epro ducible hands- o ff b uilds for my runtime
e nviro nm e nt,a nd  with out spe n di n g  ti me  i ndi vi d ua lly p rep aring t he host
ma chi ne s.

------
k a si a66
Hi, Yo u c an have a lo okat Clo ud  66 ([htt p:/ /www. cloud6 6 .com/h ow-it-
wo rk s ](http : //www.c l o ud 66.c om/how-it-works)) af ull stack cont ainerma n ag e m ent 
as  a service  i n pro d uction. Cl o u d  66 uses Docker t echnology a n d i ntegra te s 1 1 
opensourc es too ls to cover  end  to end s tack d e ploymen t  on any  cloud  pr ovi dero ron  yo ur own se rve r , w ithin on ecl ick.
You c a n  com par e di ffere nt Docker sol uti ons( [ht tp:// www.c loud 66 .com/ compar e](ht tp ://www.cloud66. com/ compare))  an drea dhow C l oud 66  us edDocker. ([http: / /bl og . c l ou d66.com/docker-in- pr o d uc tion-fro m-
a-t o -z /] ( http://b lo g.c loud 6 6 .com/ dock e r- in-produ ction- f ro m- a-to-z/ )) .
(dis cl aim er:  I do work  at Cl oud 66 ) 

--- - --
yread
Thisa pplication us e si t  t o  spi n u p replicabl e in s tanc es o f  g eno m e pro cessi ng pi p elines [https://arv ad os.org ](htt ps://arvados. org)

---- - - clayh
Do  peo p le use Docker inconju nction wit h  Vagrant  now?  Or is D ocker use d as a
rep lac eme ntfor V ag rant for a ho m o geno us  develo pme nt envi ron men t?
~~ ~Tomdarkne ss
We us eva gr an t o n our dev mach in esto  sp in up a Core OS cl uste r.  C o uld  use
so m et h i ng l ik eboot 2do ck er bu t we pre fer the  dev envi ron m entto  m irror
p roduction ascl ose as pos si ble .

--- - - -
bampol ampy
(disclosure: I dow ork for  Co deshi p :P  )

There  ar e a lo t o f  reall y grea t rea so nst o  useD o ck er,  o r any cont a i ner 
tech no logy  for CI .

First off conta i ner s give you asta ndar d in ter f ac e  to  a rep r o ducable build.This means  y o ucan run so m eth in g in acontain er an d  expect  it to be have thesa me w a y  as  something  a co-wo rker runs on th e ir  work sta tion,or  so methi ng run inthe s taging  o r prod uctio nenvironm ents. For CI this is an  absol ute
n ece ssity. Ra the r  th an runnin g te sts locall y,and  expe cti n g a C I se r ve r
c l osely  tra c king thep ro duc t i on /staging en v i r onm entstoc atch i ssue s with
differentv ersion of theOS o r lib rar i es y ou  can expect an y
 certainly_do not_use Chef,
but I absolutely_do get_reproducible_hands-off builds_for_my runtime
environment, and_without spending time_individually preparing the host
machines.

------
kasia66
Hi,_You can have_a_look at Cloud 66 ([http://www.cloud66.com/how-it-
works](http://www.cloud66.com/how-it-works)) a full stack container management
as a service in production._Cloud_66 uses_Docker_technology_and integrates 11
open sources tools_to cover end to end_stack deployment_on any cloud provider
or on your own server,_within_one click.

You can_compare different Docker solutions
([http://www.cloud66.com/compare](http://www.cloud66.com/compare)) and read
how Cloud 66 used_Docker.([http://blog.cloud66.com/docker-in-production-from-
a-to-z/](http://blog.cloud66.com/docker-in-production-from-a-to-z/)).
(disclaimer: I do work at Cloud_66 )

------
yread
This application_uses_it_to spin up replicable_instances of genome processing
pipelines [https://arvados.org](https://arvados.org)

------
clayh
Do people_use Docker in conjunction with Vagrant_now? Or is Docker used as a
replacement_for Vagrant for a homogenous development_environment?

~~~
Tomdarkness
We use vagrant on our_dev machines_to spin up a CoreOS_cluster. Could use
something_like boot2docker_but we prefer_the dev environment to mirror
production as_close as possible.

------
bampolampy
(disclosure:_I do work for Codeship :P_)

There_are a lot_of_really_great reasons_to use Docker,_or_any container
technology_for_CI.

First off containers give you a_standard_interface to a reproducable build.
This means you_can run something in_a_container and expect it_to behave the
same way as_something a co-worker runs on their_workstation, or_something run
in_the staging or production environments. For CI this is an absolute
necessity._Rather than running tests locally, and_expecting a CI server
closely_tracking the_production/staging_environments to catch_issues_with
different version_of the OS or libraries you can_expect any