GoogleContainerTools/jib · error · MojoExecutionException

<message from BuildStepsExecutionException>

Error message

<message from BuildStepsExecutionException>

What it means

The core Jib build steps (building and exporting the image to the Docker daemon) failed. BuildDockerMojo.execute() catches BuildStepsExecutionException and rethrows its message as a MojoExecutionException, using ex.getCause() as the root cause — so the interesting underlying error is in the 'Caused by' chain, not the top-line message.

Solutions

1. Inspect the 'Caused by' exception in the Maven output to find the real root cause and address it specifically.
2. If the cause is daemon-related, verify Docker is installed and running (docker info) — jib:dockerBuild requires a reachable daemon.
3. Re-run after fixing credentials/network issues; for cache corruption delete the Jib cache directory (default ~/.cache/google-cloud-tools-java/jib or target/jib-cache).
4. Run with -X (mvn -X jib:dockerBuild) for full stack traces when the cause chain is unclear.

// Pre-flight: docker info || echo 'Docker daemon not reachable'
// and: mvn -q jib:dockerBuild -Djib.skip=false --dry-run scenarios in CI

try {
  mvn jib:dockerBuild
} catch (MojoExecutionException e) {
  Throwable root = e; while (root.getCause() != null) root = root.getCause();
  // inspect root (e.g. registry auth, network) and retry transient failures
}

When it happens

Trigger: Any failure during the dockerBuild runBuild() pipeline: registry authentication failures pulling the base image, network errors, layer cache problems, or export errors writing to the Docker daemon — anything that makes BuildStepsRunner throw BuildStepsExecutionException.

Common situations: Docker daemon stopped or unreachable while jib:dockerBuild runs; wrong registry credentials in settings.xml; transient network failure pulling the base image; corrupted local Jib cache.

Related errors

• <message from BuildStepsExecutionException>
• Caused by
• is not an absolute Unix-style path
• is not an absolute Unix-style path
• is not an absolute Unix-style path

AI-assisted analysis of GoogleContainerTools/jib@fb949e2676 (2026-09-06). Data as JSON: /api/errors/ba82ed4c8a80c1f1. Report an issue: GitHub.

Appendix: source

Thrown at jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:167

    } catch (IncompatibleBaseImageJavaVersionException ex) {
      throw new MojoExecutionException(
          HelpfulSuggestions.forIncompatibleBaseImageJavaVersionForMaven(
              ex.getBaseImageMajorJavaVersion(), ex.getProjectMajorJavaVersion()),
          ex);

    } catch (InvalidImageReferenceException ex) {
      throw new MojoExecutionException(
          HelpfulSuggestions.forInvalidImageReference(ex.getInvalidReference()), ex);

    } catch (IOException
        | CacheDirectoryCreationException
        | MainClassInferenceException
        | InvalidGlobalConfigException ex) {
      throw new MojoExecutionException(ex.getMessage(), ex);

    } catch (BuildStepsExecutionException ex) {
      throw new MojoExecutionException(ex.getMessage(), ex.getCause());

    } catch (ExtraDirectoryNotFoundException ex) {
      throw new MojoExecutionException(
          "<extraDirectories><paths> contain \"from\" directory that doesn't exist locally: "
              + ex.getPath(),
          ex);
    } finally {
      tempDirectoryProvider.close();
      MojoCommon.finishUpdateChecker(projectProperties, updateCheckFuture);
      projectProperties.waitForLoggingThread();
      getLog().info("");
    }
  }
}

View on GitHub (pinned to fb949e2676)