Dependent dockerfiles fail to build

Description

I have a multi-module maven project, which produces two docker images. One image extends the other (using ARG and FROM)

How to reproduce

Sample repository: https://github.com/MFAshby/dockerfile-maven-problem

Clone this repo and try to build it with mvn clean install.

This is a multi-module maven project. The first module 'a' uses dockerfile-maven to produce an image. The second module 'b' also uses dockerfile-maven to produce an image, and it depends on the first module. The dockerfile in module 'b' extends the image produced by module 'a'.

What do you expect

Both docker images are built successfully.

What happened instead

The build for module 'b' fails with the below error:

[ERROR] manifest for mfashby/image-a:1.0-SNAPSHOT not found: manifest unknown: manifest unknown
[WARNING] An attempt failed, will retry 1 more times
org.apache.maven.plugin.MojoExecutionException: Could no

This occurs despite the earlier logging indicating that mfashby/image-a:1.0-SNAPSHOT had been successfully built and tagged.

Software:

docker version:


Client: Docker Engine - Community
Version:           19.03.5
API version:       1.40
Go version:        go1.12.12
Git commit:        633a0ea838
Built:             Wed Nov 13 07:29:52 2019
OS/Arch:           linux/amd64
Experimental:      true

Server: Docker Engine - Community Engine: Version: 19.03.5 API version: 1.40 (minimum version 1.12) Go version: go1.12.12 Git commit: 633a0ea838 Built: Wed Nov 13 07:28:22 2019 OS/Arch: linux/amd64 Experimental: true containerd: Version: 1.2.10 GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339 runc: Version: 1.0.0-rc8+dev GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657 docker-init: Version: 0.18.0 GitCommit: fec3683


- Spotify's dockerfile-maven version: 1.4.13

## Full backtrace

[log.txt](https://github.com/spotify/dockerfile-maven/files/4136042/log.txt)

spotify / dockerfile-maven