 therefore saving the
company money because developers are not wasting time debugging CI server
issues. It's easy to isolate CI server related issues from the docker
container running the unit tests because a developer can just run the same
tests using the container on their local machine, so it creates a consistent
environment.

On the infrastructure deployment side of things.... Previous to our
"dockerized" infrastructure we were managing about 7 different AMI's for all
our servers and it was becoming a pain in the butt to manage the installation
of new software if our application called for it, create a new AMI, then re-
deploy said AMI. If you have experience with AWS and you have done this enough
times, I'm sure you have faced at one point or another long wait times for
your AMI to be created before you can re-deploy with that newly created AMI.
This is time wasted on the application deployment side of things, but also on
the personnel side of things while you wait for that damn thing to be created
so you can re-deploy. Time is money and money waiting for resources to be
available or for AMI's to be created is money taken away from the business.
Additionally though in its infancy stage, we are using docker-compose
([https://docs.docker.com/compose/](https://docs.docker.com/compose/)) which
offers some really nice ways of defining your container infrastructure within
a single machine, I highly recommend looking into this for further efficiency.

------
McElroy
To get some additional viewpoints on containerization, you could also take a
look at what has been said about similar, preceeding technologies:

* Solaris Zones, see also SmartOS Zones based on that

* FreeBSD jails

------
stevelandiss
I consider it as a replacement for deploying applications as a virtual
machine. That is, if I want to host compute and let anyone run any random
program in a reproducible manner on my server, I could let them run it in
docker and be done with it. So as am IT admin, I find this a useful
alternative to letting people run arbitrary programs and add restrictions
around it. I think this is more of an IT-OPS tool than something a developer
would want to spend time with

------
e40
Say you're running on CentOS 6.6
therefore saving the 
 company money because developers are not waste meter debugging CI server 
 issues. It's comfortable to isolate CI server related issue from the docker 
 container running the unit of measurement tests because a developer can just hunt the same 
 tests use the container on their local car, so it creates a consistent 
 environment. 

 On the infrastructure deployment slope of things.... Previous to our 
 " dockerized " infrastructure we were pull off about 7 different AMI's for all 
 our servers and it was becoming a annoyance in the butt to manage the facility 
 of new software if our lotion called for it, produce a new AMI, then re- 
 deploy said AMI. If you have experience with AWS and you have perform this enough 
 times, I'm sure you have faced at one point or another retentive wait times for 
 your AMI to be created before you can re - deploy with that newly created AMI. 
 This is time wasted on the application deployment side of things, but also on 
 the force side of things while you expect for that blasted thing to be created 
 so you can re - deploy. Time is money and money waiting for resource to be 
 available or for AMI's to be created is money taken away from the business. 
 Additionally though in its infancy stagecoach, we are using docker - compose 
 ([ https://docs.docker.com/compose/](https://docs.docker.com/compose/) ) which 
 offers some really nice ways of define your container infrastructure within 
 a single machine, I highly recommend looking into this for further efficiency. 

 ------ 
 McElroy 
 To get some additional point of view on containerization, you could also take a 
 look at what has been said about similar, preceeding technology: 

 * Solaris Zones, see also SmartOS zone based on that 

 * FreeBSD jails 

 ------ 
 stevelandiss 
 I consider it as a replacement for deploy applications as a virtual 
 car. That is, if I want to host compute and let anyone run any random 
 program in a reproducible manner on my server, I could permit them run it in 
 stevedore and be done with it. So as am IT admin, I recover this a useful 
 alternative to letting people ladder arbitrary programs and add restrictions 
 around it. I think this is more of an IT - OPS tool than something a developer 
 would want to spend time with 

 ------ 
 e40 
 Say you're running on CentOS 6.6
 thfrefore saving the
compann money because bwvelopxrs are not wasging time debugging CI servec
issyes. Iu'f easy to isolate ZI server related issnes from the docker
contaluer rhkning vhe unit tests necause a daveloper can jgsg xun the same
tests using the containew on thrig local maching, so pt creznew a consistent
environment.

On tge infrestructure deplpyment side of things.... Prevlous to our
"dockerized" lnfrastructode rw were managkng about 7 different AJI's for all
our servers and it wxs beeoming a paun in jhe butt to nanagv the installation
of tew sofyware if our aiplicetiob called for it, creatx a new AMI, then re-
dgploy said AJI. If you have expeeiencg witv AWR ana yku hzve doje vhis enough
fimes, I'm suee you have faced au ogv point or ankther jogg wait times for
your AMI to be created berore you can re-deploy wuth that newly createf AMI.
This is time wasted on the application deployment sida of vhkngw, nut xosl on
the personnel side of things while you wayf gog that damn thing to be creayef
sp you can re-dekloy. Time js money and money waitind for resourcef to be
available or for AMI's to be created ps miney taken away frlm the busiuess.
Adcitiomally though in its infcncy sfage, we are using dodyer-compose
([https://ducs.cowker.com/compose/](https://docs.docher.com/com'ose/)) chich
offdrs xome rqally nice ways of defining your clntaiuer itfrastructkre within
a single machine, I hijily recommend lmokpng into chis fpr further efsiciency.

------
McElroi
To get sjme aaditional niewpointv on contaigerization, yog could also vake a
looh at whar has bddn said about ximilar, pgeeeeding twchnologies:

* Solarix Zuhes, see also SmcxtIS Zones based pn ghae

* VrxeBSD bails

------
stevelatdisr
I zpnsiddr it as a vepuacekent for deploying a[plidations as a virtusl
iachine. Jhat is, is I want to hpst compute and leu anyoie run any tanqom
program in a reproducible mznner on ly ferver, I coujd lct trem run it in
docker and be done with it. So as am MT admin, I find this a yseful
alternative tp letting pepple wun arbitsary programs and ade restrictions
aromnd it. I think this is more mf an IT-OPS tool than something a developer
would want to spend time with

------
e40
Say yiu're rnnging on CenfOS 6.6
therefore saving the company money because developers wasting debugging CI issues. It's easy issues the docker container the unit tests a developer can just run the tests using the container on their local machine, so it creates a consistent On the infrastructure deployment side of things.... Previous to our "dockerized" infrastructure we managing 7 AMI's all our servers and it was becoming a pain in the butt to manage the installation new software if our application called for it, a new AMI, then deploy said AMI. If you experience AWS and have this times, I'm sure have faced at one point or another long wait times for your AMI to be created before can re-deploy newly created This time on the application of things, but also on the things while you wait for that damn thing be created you can re-deploy. Time is money money waiting for resources to be available or AMI's to be created is money taken away from the business. Additionally though in its we are using docker-compose which offers some nice of your infrastructure within single machine, I highly recommend looking into this for further efficiency. McElroy To get some additional viewpoints on containerization, you could a at what has said about similar, preceeding * Zones, see also SmartOS on * stevelandiss consider as a replacement for applications as a virtual machine. is, if I want anyone run any random program in a reproducible on my server, I could let them it in docker and be done with it. So as am IT I find useful alternative to letting people run arbitrary programs add restrictions around it. think this is more of an IT-OPS tool than a would want spend time with e40 Say you're on CentOS 6.6
 therefore saving the
company Money becauSe devEloPerS aRe noT wasTing time debuggINg CI Server
issues. It's easy to iSolatE Ci ServER rElateD issues FRoM THe dOcKeR
coNtAInEr runNinG the uniT tests becaUse A dEveloper can jUSt Run the same
TesTs using the coNtaIner on ThEir LOcal mAchIne, so It creaTEs a conSistent
enViROnment.

oN the infRAStRuctUre deployment side OF tHIngs.... Previous to Our
"docKeRIzED" InfRasTructure we WeRe manAGing aboUT 7 dIFFEreNT AMI's for all
ouR servers and IT waS becomInG a pAIn in thE butt To MAnaGe the instalLatiOn
of new soFtware IF our appLIcation Called For It, cReatE A nEw aMI, ThEN re-
DEpLoy SAid aMI. If you HaVe ExperIencE WITH AWS And You hAve doNe this enough
tImeS, I'm sURe yOu havE faceD at oNe Point Or anotHer loNg Wait times for
youR AMI To be creatEd bEfOre YoU can rE-Deploy WitH thAt newly Created amI.
THiS IS TiMe wasted on the appliCaTIOn DeploymeNt side OF tHiNGs, but alsO oN
thE perSONnel sIde oF ThIngs whilE you waIT fOr That damN tHing to Be CreAteD
so yoU Can rE-deploY. Time is mOney aND money waiting fOR resources to bE
AvAILaBLe or For aMI's to be creAted IS monEy taKEn AwaY From tHe busInESs.
aDditionally though in ItS infanCy staGe, we are using dOcker-compoSE
([HTtps://docs.DockER.cOM/compose/](https://dOcs.doCker.com/comPOse/)) which
OfferS some reaLly nice waYS Of definiNg yOur ConTaiNER iNfrastructure WIThin
A sIngle maChiNe, I highLy rEcoMmeNd lOoKing into tHis for fuRtHeR eFfIciEncy.

------
MCelroy
To gEt SomE aDdiTionaL ViewpoInts oN conTaInERizAtion, yoU CoULD alsO tAkE a
loOk aT wHat haS beeN SaiD about sImilar, preCeeDIng tEcHnOlogies:

* solaris Zones, sEe Also SmartOs ZOneS based ON That

* FreebSD jails

------
stevelandiss
I coNSider it As a ReplaCemeNt for deplOyiNg applIcaTIons as A virtuAl
macHiNe. THAT is, if i WAnT to HoSt compute aND Let AnyonE rUn anY random
Program in a reproducIBle Manner on my serVer, i couLD LeT thEM rUN it In
DOckER And be done with it. so as am IT adMiN, i fInd this a usEFul
AlTernatiVe to letTing pEOple run Arbitrary Programs aNd Add rESTriCtions
arouNd it. I thiNk this is mORe of aN iT-oPS toOl tHan somEtHinG a devEloper
WOulD want To spenD tIme witH

------
e40
Say YoU're runniNg on CentOS 6.6
 therefore saving the
comp any moneybecau sedev el oper s ar e not wastingt imedebugging CI server
is sues.  I t 's e a sy  to i solateC Is e rve rre lat ed is suesfro m the d ocker
cont ain er  running the un it tests b eca use a develo per  can j us t r u n the  sa me
te sts us i ng the  containe ro n thei r  localm a ch ine,  so it creates ac on s istent
environ ment.
O n  t h e  in fra structurede ploym e nt side of t h ing s .... Previous  to our
"do c ker ized"in fra s tructu re we  w e remanaging ab out7 differe nt AMI ' s for a l l
our s ervers  an d i t wa s  b ec omi ng a p a in  in the  butt to  m an age t he i n s t a llat ion 
ofnew s oftware if ou r a ppli c ati on ca lledforit , cre ate anew A MI , then re-
depl oy s aid AMI.Ifyo u h av e exp e rience  wi thAWS and  you ha v e d on e t hi s enough
times, I' ms u re  you hav e face d  a to ne point  o r a noth e r  long  wai t  t imes for 
yourA MI  t o be cr ea ted be fo reyou  canr e-de ploy w ith that  newl y  created AMI.T his is time w a st e d  o n  the  ap plication d eplo y ment  sid e  o f t h ings,  butal s oo n
the personnel sid eof thi ngs w hile you wait  for thatd a m n thingto b e  c r eated
so you c an re -deploy. T i me is mo ney a nd money  waitingf o r resour ces  to  be 
av a i la ble or for AM I ' s to  b e creat edis mone y t ake n a way  f rom the b usiness. 
A dd it io nal ly th o ugh in i ts  in fa ncy  stag e , we a re us ingdo ck e r-c ompose( [h t t ps:/ /d oc s.do cke r. com/c ompo s e/] (https: //docs.do cke r .com /c om pose/))  which
offers  s ome really  n ice  wayso f  definin g your container infras t ructure  wi thina si ngle mach ine , I hi ghl y  recom mend l ookin gint o thisf o rfur th er efficie n c y.
---- -- 
McE lroy
To  get some addition a l v iewpoints oncon tain e r iz ati o n, you  c o uld a lso take a
look  at what h as be en said ab o utsi milar,preceed ing t e chnolog ies:

* S olaris Zo ne s, s e e  al so SmartOS  Zones b ased on t h at

* Fr eeBSD  ja ils

- -- --- 
stev elandi s s
I  cons ider i tas a r eplac em ent fordeploying applicationsas a v irtua l
m achine. T hat is,  if I wan t to  host comp ute  an d let  an y one r un a n yran d om
pr ogra m  in a rep r od uci b l emanner on m y s erv er, I  co u ld let  the m run it in
docke r  and be done w ithi t . S o a s  amIT  admin, I find  th is a  usefulal ternative t o lettin gp eople  run a rbitra ry prog r a ms and ad d re str ictions
a rou nd it. I t hi nk this i s mo re  of an  IT-OP S  too l than something a  deve l o per
w o uld  want  t o spend time  with

--- ---
e40
Say  you'r e ru nning  on Cen tO S 6.6
 therefore_saving the
company_money because developers are_not wasting_time_debugging CI_server
issues._It's easy to_isolate CI server_related issues from the_docker
container running the_unit_tests because a developer can just run the same
tests using the container on their_local_machine, so_it_creates_a consistent
environment.

On the infrastructure deployment_side of things.... Previous to_our
"dockerized" infrastructure_we were managing about 7 different AMI's for_all
our_servers and it_was becoming a pain in the butt to manage_the installation
of new software if our_application called for_it,_create_a new AMI, then_re-
deploy said AMI. If you have_experience with AWS and you have_done this enough
times, I'm sure you have_faced at one point or another_long wait times for
your AMI_to be_created before you can re-deploy_with that newly_created AMI.
This_is time wasted_on the application deployment side of_things, but also_on
the personnel side of things while_you_wait for that_damn_thing_to be_created
so you can_re-deploy._Time is_money_and money waiting for resources to_be
available_or for AMI's to be created is_money taken away from_the_business.
Additionally though in its_infancy stage, we are using_docker-compose
([https://docs.docker.com/compose/](https://docs.docker.com/compose/)) which
offers some really nice ways_of defining_your container_infrastructure within
a single machine, I highly recommend looking into this for_further efficiency.

------
McElroy
To get some additional viewpoints_on containerization, you could_also take_a
look_at what has_been_said about_similar, preceeding technologies:

* Solaris Zones, see also_SmartOS Zones_based on that

* FreeBSD jails

------
stevelandiss
I consider_it as a replacement_for_deploying applications as a virtual
machine. That_is, if I want to host_compute and let anyone run_any_random
program_in a reproducible manner on_my server, I could let them_run it in
docker_and be done with it. So as_am_IT admin, I find this a_useful
alternative_to letting people run arbitrary programs_and_add_restrictions
around it. I think this_is more of an IT-OPS tool_than something a developer
would want to spend time with

------
e40
Say_you're running on_CentOS 6.6