Hello all,

I am facing the same issue as described, running on a Jenkins instance as gradle task with plugin on version 3.3.1. Briefly these are the stages:

1. Create a docker image, using an another existing base docker image which is located to a remote registry (creating an extra layer via a Dockerfile with some stuff on top of that base docker image).

2. Use jibDockerBuild gradle task having as:
   from { image = "docker://" + [dockerImageName that was just built on stage1] }

3. Stuck having the exact described issue. It gets stuck at 25% > processing base image {IMAGE_NAME}

This is occured like 3/5 pipeline triggers and I need to find a workaround or get the provided fix for this bug ASAP - since this is getting really annoying :/ .

Thanks a lot, and especially you @EternalWind for providing a solution for that bug :) .

@athtsio Since they are unlikely to be merging my fix any time soon, one workaround we have been using is docker's multi-stage build.

We base the final image on a much simpler base image, e.g. a minimal Alpine image, instead of the desired base image. Then, we use the desired base image as a builder image and copy out all of the desired files from it since the instructions from a builder image are not going into the final image.

Of course, this is based on the assumption that most of the instructions you want from the desired base image are installing packages or copying files.

Hopefully the fix could be merged soon.

@EternalWind thanks for the response/suggestion.
We are using some kind of builder pattern.

The base image is really minimal. It is built and published in a registry. This means that we do not have to build this base image each time we need to dockerize the app. We take it/use it as is in the one single FROM in the Dockerfile.

On top of that base image, we built the image that will be used from the jib task which is like the base image plus 3 new packages installed, copy and run a script that imports the aws rds certificates. Nothing more !

My point is that the instructions are literally 10 lines.
From my point of view, I see nothing extreme in the Dockerfile to switch to multi stage build pattern :/

I do not know if by adding --no-cache on docker build will bring any difference...or make things worse 😭