(WSL2) docker build "output clipped, log limit 1MiB reached"

[fcharron83]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Actual behavior

When performing lengthy docker build operations using DOCKER_BUILDKIT=1 (but not buildx), the command stops outputting logs with the output clipped, log limit 1MiB reached message, until the build is over.

Expected behavior

Allow customization of this 1MiB log limit setting either via a config file, or the Docker Desktop - Docker Engine settings page.

Information

• Windows Version: Windows 10 Enterprise, version 20H2 (OS Build 19042.867)
• Docker Desktop Version: 3.2.2 (61853)
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No, native Windows

Problem is reproducible, and AFAIK is not new.

A similar issue has been opened for docker buildx, but I am not running buildx because it is experimental and I am in a production environment.

Steps to reproduce the behavior

1. Start a lengthy DOCKER_BUILDKIT=1 docker build... operation that produces a lot of output logs on stdout/stderr (no flags except --tag and --file)
2. Notice the output clipped, log limit 1MiB reached, and the absence of output afterward

[stephen-turner]

Thanks for the ticket. Unfortunately there's nothing we can do in Docker Desktop about this, as these components are all just upstreams to us. You could file a ticket in moby/moby (which owns docker build) but actually it's probably easier just to ask on the existing buildx ticket.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked