So I don't know enough about Docker internals/configuration requirements but I have a question. Is installing a JRE in each Docker container the common practice as opposed to some mechanism for sharing it? The JRE alone is 180MB.
This might be a quibble but I'm not sure I'd characterize Karaf as an application server. Depends on your audience I think. Brad -----Original Message----- From: CodeCola [mailto:prasen...@rogers.com] Sent: Wednesday, January 11, 2017 2:07 PM To: user@karaf.apache.org Subject: Levels of Containerization - focus on Docker and Karaf Not a question but a request for comments. With a focus on Java. Container technology has traditionally been messy with dependencies and no easy failsafe way until Docker came along to really pack ALL dependencies (including the JVM) together in one ready-to-ship image that was faster, more comfortable, and easier to understand than other container and code shipping methods out there. The spectrum from (Classical) Java EE Containers (e.g. Tomcat, Jetty) --> Java Application Servers that are containerized (Karaf, Wildfly, etc), Application Delivery Containers (Docker) and Virtualization (VMWare, Hyper-V) etc. offers a different level of isolation with different goals (abstraction, isolation and delivery). What are the choices, how should they play together, should they be used in conjunction with each other as they offer different kinds of Containerization? <http://karaf.922171.n3.nabble.com/file/n4049162/Levels_of_Containerization. png> -- View this message in context: http://karaf.922171.n3.nabble.com/Levels-of-Containerization-focus-on-Docker -and-Karaf-tp4049162.html Sent from the Karaf - User mailing list archive at Nabble.com.
