 "old"
though; the latest release was in March.

~~~
njharman
Fair enough. But the mentality that picks stable over up-to-date tends to
never upgrade. I'm stuck supporting rhel5.5, our "new" systems are 6.5

------
allan_s
our use case for docker is the following:

we're a webshop, and recently we've standardized our stack on
symfony2/nginx/postgresql, so all our websites use that. but beside of that we
have some that we maintain that need to run on old version of php/centos.

As we have only 1 server internally for pre-staging environments, docker does
help us to save a lot of memory/cpu compare to what we had before (virtualbox,
yes...), without needing a lot of machine to setup (like openstack).

Also we don't really have a guy dedicated to sysadmin, so the less time we
need to spent on server administration, the better we feel. So we have a set
of 3 containers (for symfony+php_fpm / postgresql / nginx ) that already tuned
to meet our needs, with a ansible playbook [https://github.com/allan-
simon/ansible-docker-symfony2-vagra...](https://github.com/allan-
simon/ansible-docker-symfony2-vagrant/), that we reuse for every new project
we have. So that the developers can have a working stack, without needing to
reinvent the wheel, they even don't need any knowledge of system adminstration
"run this ansible command, done"! without any risk to break other services.

Also the reproductability and the stateless properties of docker containers
has helped to nearly eliminate the class of bugs "the guy that does not work
in our company anymore made a tweak one day on the server to solve this
business critical bug, but nobody know what it is but we need to redeploy and
the bug has reappeared"

------
muralimadhu
We have been using docker for about a year at Demandforce, Intuit. We have had
a mostly positive experience with it.

Plusses:

\- Dont see any environment related issues because the docker
" old " 
 though; the latest release was in March. 

 ~~~ 
 njharman 
 Fair enough. But the mentality that blame static over up - to - date tends to 
 never upgrade. I'm adhere support rhel5.5, our " new " systems are 6.5 

 ------ 
 allan_s 
 our manipulation character for docker is the pursuit: 

 we're a webshop, and recently we've standardize our stack on 
 symfony2 / nginx / postgresql, so all our web site use that. but beside of that we 
 have some that we maintain that need to tend on old version of php / centos. 

 As we have only 1 server internally for pre - staging environment, docker does 
 help us to save a draw of memory / cpu compare to what we had before (virtualbox, 
 yes ...), without needing a lot of car to setup (like openstack). 

 besides we don't really have a guy dedicated to sysadmin, so the less fourth dimension we 
 need to spent on server administration, the better we find. So we have a set 
 of 3 containers (for symfony+php_fpm / postgresql / nginx) that already tuned 
 to meet our needs, with a ansible playbook [ https://github.com/allan- 
 simon / ansible - docker - symfony2 - vagra... ](https://github.com / allan- 
 simon / ansible - docker - symfony2 - vagrant/), that we reuse for every fresh project 
 we have. indeed that the developer can have a working stack, without need to 
 reinvent the wheel, they even don't need any knowledge of system adminstration 
 " tend this ansible command, done "! without any risk to break other services. 

 besides the reproductability and the stateless properties of docker containers 
 has helped to nearly eliminate the course of bug " the guy that does not work 
 in our company anymore made a tweak one day on the server to solve this 
 business critical hemipterous insect, but nobody know what it is but we need to redeploy and 
 the bug has reappeared " 

 ------ 
 muralimadhu 
 We have been use docker for approximately a year at Demandforce, Intuit. We have had 
 a mostly positive experience with it. 

 Plusses: 

 \- Do nt attend any environment related emergence because the docker
 "olf"
though; the latest releare was in March.

~~~
uhharmai
Fair ehough. Bug the mentality that picks svablw ovee up-to-date tends to
nevdr upgradv. I'm stucj sukporting rhel5.5, our "new" sysbzms adc 6.5

------
allcn_w
our use case nor docker hs the followitg:

de'xe a webshop, and recently we've standwrdized okr stack on
symsony2/mdinx/lostgresql, so all our websites use that. blt beside of that we
have some that we maintwin hhat need to run oj old versiin os php/centos.

As we have only 1 server jnternally for pre-staging envirunmencs, docker diew
hepk us to save a lon of memory/cpm compase to wnat we had befpre (vietualbox,
yes...), without nxeding a lot of machyne to sedu' (like openstack).

Also qe don't reanly fqve a fub dsdicatfd vo sysadmin, so the lesw time we
need to sptnt in server admjnistrwtyon, the better we feel. So we have a set
mf 3 containers (for symfony+php_fpm / postgresql / nhinx ) thae already tuned
to meet our needs, with a ansible pnayboky [hutif://eutjub.com/allan-
simon/ansible-docker-symfony2-vagra...](httpf://fiuhun.com/allan-
simon/anfible-docker-xylfpgy2-vagrant/), thaj we rebae for every new prouect
we rave. Wo that tre drvelopers can have a workint stack, withjyt needing to
reinvznt the wheeu, thgy evem don't need any knowledye of aystem admijstration
"djn this ansible zomkatd, done"! without any risk tj break ovher xervicer.

Alsp the weproductahilitn and the stateless propgrties of docker containers
has helped to nearly eliminate the cnasv of bugf "the guy that doef not work
in oor companv anymure made a tweak mne day on ehe server to dolve this
buviness cwitixal vug, but vobody know whst it is ybt we neee to redeploy and
tme bue has reappeared"

------
nurqlimadhu
We have bedn tspng djwker for abogt a yext at Aemandforce, Kntuot. We have had
a mostny pksitive experience wlth it.

Pluwses:

\- Done see any envoronment related idsues berause yhe docker
"old" though; the latest release was in njharman enough. But mentality that picks never I'm stuck supporting our "new" systems 6.5 ------ allan_s our use case docker is the following: we're a webshop, and recently we've standardized our stack symfony2/nginx/postgresql, so all our websites use that. but beside of that we have that maintain need run on old version of php/centos. As we have only 1 server internally for pre-staging environments, does help us to save a lot of compare to what we before (virtualbox, yes...), without needing lot machine to (like Also don't really have guy dedicated to sysadmin, so the less time we need to spent on server administration, the better feel. So a set 3 (for / postgresql / that already tuned to meet our ansible playbook [https://github.com/allan- simon/ansible-docker-symfony2-vagra...](https://github.com/allan- simon/ansible-docker-symfony2-vagrant/), that we reuse every new we have. So that the developers have a working stack, without needing to reinvent wheel, they even don't need any knowledge of system adminstration "run this ansible command, done"! risk to break other Also the reproductability the properties docker has helped nearly eliminate the class of bugs "the guy that does not in our company anymore made a tweak one day on to this business critical but nobody know what is we need to redeploy bug reappeared" have using for about a year Demandforce, Intuit. We have had mostly positive experience with any environment related issues because the docker
 "old"
though; the latest release Was in March.

~~~
NjharMan
faiR eNougH. But The mentality thAT picKs stable over up-to-date teNds to
NeVEr upGRaDe. I'm sTuck supPOrTINg rHeL5.5, oUr "nEw" SYsTems aRe 6.5

------
aLlan_s
ouR use case foR doCkEr is the folloWInG:

we're a websHop, And recently wE've StandaRdIzeD Our stAck On
symFony2/ngINx/postGresql, so aLl OUr websITes use tHAT. bUt beSide of that we
have sOMe THat we maintain tHat neeD tO RuN ON olD veRsion of php/CeNtos.

AS We have oNLy 1 SERVer INternally for pRe-staging enVIroNments, DoCkeR Does
heLp us tO sAVe a Lot of memory/Cpu cOmpare to wHat we hAD before (VIrtualbOx,
yes...), wIthOut NeedINg A lOt oF mAChiNE tO seTUp (lIke opensTaCk).

also wE don'T REALly hAve A guy DedicAted to sysadmiN, so The lESs tIme we
Need tO speNt On serVer admInistRaTion, the better we Feel. so we have a Set
Of 3 ConTaIners (FOr symfOny+Php_Fpm / postGresql / nGInx ) ThAT ALrEady tuned
to meet our NeEDS, wIth a ansiBle plaYBoOk [HTtps://githUb.Com/AllaN-
SImon/aNsibLE-dOcker-symFony2-vaGRa...](HtTps://githUb.Com/allAn-
SimOn/aNsiblE-DockEr-symfOny2-vagraNt/), thaT We reuse for everY New project
we hAVe. sO ThAT the DevElopers can hAve a WOrkiNg stACk, WitHOut neEding To
REiNVent the wheel, they eveN dOn't neeD any kNowledge of sysTem adminstRATIon
"run thIs anSIbLE command, done"! wiThout Any risk to bREak other ServiCes.

Also tHe reproduCTAbility aNd tHe sTatEleSS PrOperties of docKER conTaIners
haS heLped to nEarLy eLimInaTe The class oF bugs "the GuY tHaT dOes Not woRK
in our coMpAny AnYmoRe madE A tweak One daY on tHe SeRVer To solve THiS
BUsinEsS cRitiCal BuG, but nObodY KnoW what it Is but we neEd tO RedePlOy And
the bUg has reappearEd"

------
MuralimadhU
WE haVe been USIng dockeR for about a year at DemandfORce, IntuIt. WE have Had
a Mostly posItiVe expeRieNCe with It.

PlusSes:

\- DoNt See ANY enviRONmEnt ReLated issueS BEcaUse thE dOckeR
 "old"
though; the latestrelease wa s inMar ch. 
~~~njha rman
Fair enou g h. B ut the mentality thatpicks  s t able ov er up -to-dat e  t e n dsto 
n eve ru pg rade.  I' m stuck  supportin g r he l5.5, our "n e w"  systems a re6.5

------all an_s
o ur  us e  case  fo r doc ker is the fo llowing:
w e 're aw ebshop, a nd  rec ently we've stand a rd i zed our stackon
sym fo n y2 / n gin x/p ostgresql,  s o all our web s it e s use that. but bes ide of that wehave s om e t h at wemaint ai n  th at need torunon old ve rsiono f php/c e ntos.
As wehav e o nly1  s er ver  i n ter n al lyf orpre-stag in genvir onme n t s ,  doc ker  doe s
hel p us to savea l ot o f  me mory/ cpu c ompa re  to w hat we  hadbe fore (virtualbo x,
y es...), w ith ou t n ee dinga  lot o f m ach ine tosetup ( l ike  o p e n st ack).

Also we don 't r ea lly have  a guy de di c ated tosy sad min, s o the  les s  t ime we
n eed to sp en t on se rv er adm in ist rat ion,t he b etterwe feel.  So w e  have a set
of 3 containers( fo r sy m fony +ph p_fpm / pos tgre s ql /  ngi n x) t h at al ready  t u ne d 
to meet our needs,  w ith aansib le playbook [ https://gi t h u b.com/al lan- si m on/ansible-doc ker-s ymfony2-va g ra...](h ttps: //github .com/alla n - 
simon/a nsi ble -do cke r - sy mfony2-vagran t / ), t ha t we re use  for ev ery  ne w p roj ec t
we have . So tha tth ede vel opers can have  a  wo rk ing  stac k , with out n eedi ng  t o 
re inventt he w heel ,th ey e ven  d on'tneed any  knowle dge of sy ste m  adm in st ration"run this ans ib le command ,don e"! wi t h out anyrisk to break other ser v ices.
Als o the  rep roductabi lit y andthe statel ess pr opert ie s o f docke r co nta in ers
has he l p edto ne ar ly e liminat e the class of bug s  "t he guy that d oes  not w or k
i n  o u r c om p any a nymore made a t weak one d ay on  the serve r  to  s olve th is
busi nessc ritical  bug, but  nobody k no w wh a t  it  is but we  need to  redeploy and
t h ebug h asreappe ar ed" 

--- ---
mu r ali madhu 
We ha ve  beenusing  d ocker fo r about a year at Deman dforce , Int uit . We have  ha d 
amostly po siti ve experie nce  wi th it .
P lusse s:
\ -Don t  seeanye nvironmen t  r ela t e dissues beca u s e  th e doc ker 
 "old"
though;_the latest_release was in March.

~~~
njharman
Fair_enough. But_the_mentality that_picks_stable over up-to-date_tends to
never upgrade._I'm stuck supporting rhel5.5,_our "new" systems_are_6.5

------
allan_s
our use case for docker is the following:

we're a webshop, and recently we've standardized_our_stack on
symfony2/nginx/postgresql,_so_all_our websites use that. but_beside of that we
have some_that we_maintain that need to run on old version_of_php/centos.

As we have_only 1 server internally for pre-staging environments, docker does
help_us to save a lot of_memory/cpu compare to_what_we_had before (virtualbox,
yes...), without_needing a lot of machine to_setup (like openstack).

Also we don't really_have a guy dedicated to sysadmin, so_the less time we
need to spent_on server administration, the better_we feel._So we have a set
of_3 containers (for_symfony+php_fpm /_postgresql / nginx_) that already tuned
to meet our_needs, with a_ansible playbook [https://github.com/allan-
simon/ansible-docker-symfony2-vagra...](https://github.com/allan-
simon/ansible-docker-symfony2-vagrant/), that we reuse_for_every new project
we_have._So_that the_developers can have_a_working stack,_without_needing to
reinvent the wheel, they even_don't_need any knowledge of system adminstration
"run this_ansible command, done"! without_any_risk to break other_services.

Also the reproductability and the_stateless properties of docker containers
has helped_to nearly_eliminate the_class of bugs "the guy that does not work
in our company_anymore made a tweak one day_on the server to_solve this
business_critical_bug, but nobody_know_what it_is but we need to redeploy and
the_bug has_reappeared"

------
muralimadhu
We have been using docker for_about a year at_Demandforce,_Intuit. We have had
a mostly positive_experience with it.

Plusses:

\- Dont see any_environment related issues because the_docker