如何配置docker-java将Docker操作日志输出至Windows控制台？

Yep, you absolutely can get those Docker build logs to show up in your Windows console—your current code is missing a log handler that captures the stream output from Docker's build process. Here's how to tweak your build method to fix this:

import java.nio.charset.StandardCharsets;
import java.util.HashSet;
import java.nio.file.Path;

public String build(String name, Path dockerFilePath) throws InterruptedException {
    System.out.println("Building image from: " + dockerFilePath.toString());
    var tags = new HashSet<String>();
    tags.add(name);

    return client
        .buildImageCmd()
        .withNoCache(true)
        .withDockerfile(dockerFilePath.toFile())
        .withTags(tags)
        // Add this log handler to capture and print build output
        .withLogFrameHandler(logFrame -> {
            // Print standard build output (e.g., step details)
            if (logFrame.getStream() != null && !logFrame.getStream().trim().isEmpty()) {
                // Use UTF-8 explicitly to avoid garbled text on Windows
                System.out.print(new String(logFrame.getStream().getBytes(), StandardCharsets.UTF_8));
            }
            // Print build errors (shows up in console stderr)
            if (logFrame.getError() != null && !logFrame.getError().trim().isEmpty()) {
                System.err.print(new String(logFrame.getError().getBytes(), StandardCharsets.UTF_8));
            }
            // Print progress updates (e.g., layer download status)
            if (logFrame.getProgress() != null && logFrame.getStatus() != null) {
                System.out.printf("%s: %s%n", logFrame.getStatus(), logFrame.getProgress());
            }
        })
        .start()
        .awaitCompletion()
        .awaitImageId();
}

Key Details: #

• The withLogFrameHandler method hooks into every log frame generated during the Docker build process. It lets you handle different types of output directly:
  • Stream: Regular build steps and informational messages (matches what you'd see in the Docker CLI)
  • Error: Build failures or warnings that would appear in red in the CLI
  • Progress: Updates about layer downloads, extraction, or image creation
• The explicit UTF-8 encoding fixes common garbled text issues on Windows, since Docker outputs logs in UTF-8 by default.

Quick Checks: #

• Confirm your Docker daemon is actually running and listening on tcp://localhost:2375 (you already set this in your config, but double-check if the daemon is accessible)
• If you still don't see logs, verify that your Dockerfile produces output during build (some minimal images might not generate much log content)

内容的提问来源于stack exchange，提问作者Ryan Lundy