That's been my view, it's something that can be used to make deployments a little easier, not as a "I don't have to try to write decent, non-monolithic code anymore". A lot of others are vocally expressing this sort of opinion. It actually feels like a this sort of thing happens a lot. A new technology comes along, makes it easy to get a turd of a piece of software up and running, magically everything goes out the window until the fad passes.
I saw someone describe this sort of phenomena in a great way, wish I could find it to quote him. I certainly have no problem if others want to use the latest fad, I don't like how people push the newest fad on everyone rather than let people decide for themselves. On Apr 8, 2015 11:12 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net> wrote: > I see your point. > > But IMHO, I don't see anything new with Docker, just a easier or more > convenient way to do what you do with Solaris Zone, Linux jail/xen, and vm > like VirtualBox and vmWare ;) > > So, Docker itself doesn't provide an application container: it provides an > system container. > > Of course, you can always start a Docker image with just a JVM for your > application, for instance bootstrapping Jetty, etc. Or you can just > bootstrap an application container (like Karaf ;)), ready to host your > applications. > > My $0.02. > > Regards > JB > > On 04/08/2015 04:58 PM, Ryan Moquin wrote: > >> I actually pop by your blob periodically to see if you have posted >> anything new. Your blog post on Karaf and Docker is initially what made >> me want to look into and understand how Docker could benefit Karaf. As >> I've been reading other sources, I'm becoming less optimistic about how >> Docker benefits Karaf. >> >> As Vincent mentioned, cloud computing and virtualization are already >> using a similar approach. I guess I'm wondering why we need to add yet >> another virtualization container on top of another. >> >> Ryan >> >> On Wed, Apr 8, 2015 at 10:12 AM, Jean-Baptiste Onofré <j...@nanthrax.net >> <mailto:j...@nanthrax.net>> wrote: >> >> Hi Ryan, >> >> I invite you to read my blog about Karaf and Docker: >> >> http://blog.nanthrax.net/2014/__12/apache-karaf-christmas-__ >> gifts-docker-io-profiles-and-__decanter/ >> <http://blog.nanthrax.net/2014/12/apache-karaf- >> christmas-gifts-docker-io-profiles-and-decanter/> >> >> and the Karaf Docker proposal: >> >> http://karaf.922171.n3.nabble.__com/DISCUSSION-Karaf-docker- >> __io-td4038470.html >> <http://karaf.922171.n3.nabble.com/DISCUSSION-Karaf- >> docker-io-td4038470.html> >> >> Regards >> JB >> >> >> On 04/08/2015 02:31 PM, Ryan Moquin wrote: >> >> Hi, >> >> I've been reading up on Docker and trying to understand what all >> the >> fuss is about (I'm still not sure for several reasons, but I >> digress). >> I was wondering how Docker might influence Karaf in the future >> as well >> as how Docker fits in with OSGi and Karaf in general. >> >> Specifically my questions are: >> >> 1. It seems like the hype of Docker is causing people to shy >> away from >> the dynamic nature of OSGi, such as being able to update bundles >> in a >> running Karaf container. Is the use of Docker and Karaf boiling >> down to >> creating a static Karaf image and anytime you want to upgrade >> anything, >> you throw away the instance and replace it with a newly built >> instance? >> It feels inefficient. It also feels like it really complicates >> everything. Unless you are developing on Linux, development using >> Docker containers is really slow. Dealing with setting up docker >> containers to test things out locally also seems like a lot of >> overhead. If you don't test locally with Docker, then can you >> be sure >> that deploying in a Docker container will work properly? >> >> 2. In regards to the first question, and the fact that people >> indicate >> they think Docker will become the standard, will Karaf be dumbed >> down in >> the future due to the static nature of Docker? Meaning, if Docker >> *does* becomes the de factor standard for deploying everything, >> it feels >> like developers would be discouraged from using a lot of the >> run-time >> benefits OSGi offers. >> >> I kind of feel like the big push of Docker in the development >> community >> in general (as a whole, not talking about the Karaf developer >> community), will potentially cause a lack of innovation and >> improvements >> in the deploying of applications. Docker could become a >> crutch. If an >> application is slowly leaking memory over a 24 hour period, why >> fix it? >> When it crashes, just replace it with a new instance. >> >> Am I wrong? This is just my initial thoughts and questions. I >> wanted >> to see what other people thought and how other people view >> Docker and >> Karaf being used or how it is being used. >> >> Ryan >> >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org <mailto:jbono...@apache.org> >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
