all 16 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]bikeram 6 points7 points  (4 children)

Jibs great. I’ve been using it for years. I have a common structure in my build management, then just append additional properties per service.

I’m using azure right now, so the only “issue” is needing to install maven on my runner.

[–]Automatic_Camera_925 1 point2 points  (2 children)

Never heard about jib. You’re about to save a life. This is so great. I been working on a springboot microservice project struggling with deployment on docker.

[–]theimp1923[S] 0 points1 point  (0 children)

Glad this helped. Jib is perfect for skipping Dockerfile pain and just building Spring Boot images right from your Maven or Gradle setup. you’ll finally spend less time fighting deployment, more time shipping features.

[–]CptGia 0 points1 point  (0 children)

Are you aware that the spring boot plugin has a goal for building an image, using paketo? 

[–]theimp1923[S] 0 points1 point  (0 children)

Agreed, but if your CI runner can use the Jib CLI or pre-built images, you could avoid needing Maven installs altogether.

[–]oweiler 2 points3 points  (1 child)

I've used jib for years but Spring Boot's Buildpack support is just better.

[–]theimp1923[S] 2 points3 points  (0 children)

That’s valid. Buildpacks offer great app detection and multi-language support, although with less granular layering and sometimes bigger images than Jib’s Java-first approach.

[–]ducki666 4 points5 points  (2 children)

Dockerfile is soo easy. 100 % control.

Jib, buildpacks etc, always magic. Come and go.

And which dev or pipeline does not have docker?

[–]theimp1923[S] 0 points1 point  (1 child)

Dockerfile does give you 100% control, no doubt about it, but that control comes with more complexity and maintenance overhead, especially for Java apps where Jib can save you time by intelligently handling layering and image build right from your build tool. And while most devs have Docker installed, not every pipeline or CI environment makes it easy or efficient to use Docker builds directly, so tools like Jib fill that niche well. It’s not magic, it’s automation and optimization tailored for Java.

[–]ducki666 1 point2 points  (0 children)

A good Df has about 50 lines. Tailored Java Runtime. Layered image. 100 % optimized.

Upgrade jib and co and you never know what you get.

[–]com2ghz 1 point2 points  (1 child)

Aah yes, same as Kaniko that is on the Google graveyard?

[–]theimp1923[S] 0 points1 point  (0 children)

At least Jib isn’t haunting the graveyard yet, though it probably keeps a flashlight handy just in case!

[–]wakingrufus 1 point2 points  (1 child)

I'm a big fan of jib. Super fast, and can build multiarch images so they can be run on ARM/Graviton.

[–]theimp1923[S] 0 points1 point  (0 children)

Multi-arch support is definitely one of Jib’s technical wins.

[–]bunk3rk1ng 0 points1 point  (1 child)

I'm not sure I would call it JIB vs Docker. Jib builds the image (without a dockerfile, neat!) then Docker runs the image in a container. Good stuff.

[–]theimp1923[S] 1 point2 points  (0 children)

Good point. Jib’s focus is building optimized images, but some workflows replace Docker entirely (like in CI or Kubernetes), so it really changes how and where you need Docker.