Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: "<image> must have a non-null <name>"

See original GitHub issue

Description

I have define this plugin section:

<plugin>
				<groupId>io.fabric8</groupId>
				<artifactId>docker-maven-plugin</artifactId>
				<version>0.17.2</version>
				<configuration>
					<images>
						<image>
							<alias>galan</alias>
							<name>cdp/galan</name>
							<external>
								<type>compose</type>
								<basedir>docker</basedir>
								<composeFile>docker-compose.yml</composeFile>
							</external>
						</image>
					</images>
				</configuration>
</plugin>

Info

When I do:

mvn clean docker:build

I get the following error:

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.17.2:build (default-cli) on project   galileo-anagrafica-rapporto-services: Execution default-cli of goal io.fabric8:docker-maven-plugin:0.17.2:build failed: Configuration error: <image> must have a non-null <name> -> [Help 1]

d-m-p version : 0.17.2
Maven version (mvn -v) :

Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_111, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: it_IT, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-45-generic", arch: "amd64", family: "unix"

Docker version :

Issue Analytics

State:
Created 7 years ago
Comments:16

Top GitHub Comments

2reactions

habzitounicommented, Jul 25, 2017

Hi, @rhuss : i have the very same issue with the 0.20.0 version of the plugin. Any update on the source of the problem ?

1reaction

timothybasanovcommented, Jan 20, 2018

Yep. Looks like I’m affected as well. I debugged plugin code a bit (turns out it’s as easy as use mvnDebug instead of mvn on the cmd line):

At least one NPE issue is here io.fabric8.maven.docker.config.handler.compose.DockerComposeConfigHandler#getImageName My workaround was to set pom.xml/alias to match “name” from docker-compose (for the image that requires a build and is not just pulled so it does not have “image”), then pom.xml/name would be used for that image and it can be non-null.

Unfortunately in my case there were some weird issues around <wait/> configs, so I ended up switching to exec plugin with shell scripts calling docker-compose directly.

Top Results From Across the Web

IllegalArgumentException : image must be non-null

I'm working on a simple "Space Invaders" game using JavaFx, and while my game works fine without any exceptions or errors when I...

Improve code inspection with annotations - Android Developers

Learn how annotations allow you to provide hints to code inspections tools like Lint, to help detect these more subtle code problems.

Error generating chart: No features contain non-null values of ...

I introduced an arbitrary 'system:time_start' (ee.Date('2014-09-01')) in that image (code) and it can be corroborated there is no series for ...

Safe calls(?.) vs Null checks(!!) in Kotlin - Suneet Agrawal

variable = null //compilation error ... //the variable can't be null ... in turn may have another Employee as a department head, then...

ImagePattern can't be created when base image loaded in ...

Type: Bug. Status: Closed ... It can not be used for ImagePattern because of runtime exception: java.lang.IllegalArgumentException: Image must be non-null