I'm thinking more of replacing existing education system with JetBrains one. They can start with my country's education system anytime, because selling out to Microsoft didn't work so well.
The quality of the video, the design of the graphics, crystal clear explanation right to the point, and even soft background music make this video outstanding. Thank you
Nice presentation. I want to add at 5:50 VMs don't suffer only from having to duplicate an OS but also from having to emulate hardware components to the virtual environment. That makes them both heavy and slow.
@Dalia Abo Sheasha I was more thinking along the lines of how to actually create a good image (not with Dockerfile, IMHO); how to configure the Java application through container interfaces; changed assumptions, e.g. short-running small service vs long-running monolith, and consequences; health checks resp. liveness/readiness probes and good practices for them; delegating cross-cutting concerns, e.g. to service mesh; and so on. In short, there's many things you have to rethink when deploying a container image to, say, a Kubernetes cluster, as opposed to running a WAR in an application server. Just bundling your old application in a Dockerfile is, arguably, not even a good start. :'D That doesn't take away anything from your video, of course: as I said, it is a good, approachable intro into the "why" of containers, which is often lost in more technical contributions about "how".
Great video and material quality. This kind of format works even better than just a tutorial from Docker. And big thanks for showing us how to use Docker features from IDE. P.S: and it's easy to consume a material at 2x. Thanks to Dalia for the great pronunciation!
This is useful as currently, we do not have tutorials that clearly explain Java with Docker. Keep it up. However, we would like Tutorials that are more hands-on from your side than you explaining and the code writing itself on the left. None the less thanks so much.
Good video. For the building step once you made changes, I thought it was good that you built locally to show the updated files, but think it would have been better if you had gone into detail that you could update the docker file to add a build step for you. So you can make sure the code builds from within the container as well not just it builds on my box, which would help illustrate that someone else could build & run the application.
I ran into some issues, specially when it comes to running the containers. I believe the following points will help others following this tutorial. If your Main java class is within a package, make sure that within the DockerFile, you include completely qualified java-package + java-class name. I had to do...CMD java com.test.docker Main (as my Main class was within the com.test.docker package). Also, when executing the image, I had to include version numbers. So docker run :
If anyone gets error following this tutorial Error: Could not find or load main class Main Solution: Change CMD java Main to CMD java com.example.Main Replace com.example according to your package.
this video cleared a lot of stuffed air for me, thank you... trying to run my container after I have built it, I get this [Error: Could not find or load main class EazyBankApplication] I need help on this
![Intro to Docker [with Java Examples]](/img/logo.svg){kind=logo}
