(WSL2) docker build "output clipped, log limit 1MiB reached" #42261
Description
Description
When performing lengthy docker build operations using DOCKER_BUILDKIT=1 (not using buildx, as it is experimental), the command stops outputting logs with the "output clipped, log limit 1MiB reached" message, until the build is over.
(This was first opened on docker/for-win#10839, but I've been instructed to open it here instead)
Steps to reproduce the issue:
DOCKER_BUILDKIT=1 docker build ....that produces more than 1MiB of logs on stdout/stderr
Describe the results you received:
- Last output line says "output clipped, log limit 1MiB reached"
- No more log output in the terminal until the build is finished.
Describe the results you expected:
- Continuous log output in the terminal
- Or, clear instructions on how to increase that limit using stable functionality
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client: Docker Engine - Community
Version: 20.10.3
API version: 1.41
Go version: go1.13.15
Git commit: 48d30b5
Built: Fri Jan 29 14:33:13 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.5
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: 363e9a8
Built: Tue Mar 2 20:15:47 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.3
GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Output of docker info:
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc., v0.5.0)
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 7
Server Version: 20.10.5
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.4.72-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 15.63GiB
Name: docker-desktop
ID: 3DGW:YZBD:OHOU:UUWW:J2JR:XV2Z:GCIF:3P43:6YAU:IJOX:7MAL:E2DI
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 49
Goroutines: 52
System Time: 2021-04-06T19:23:48.7791219Z
EventsListeners: 3
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
localhost:5000
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
Additional environment details (AWS, VirtualBox, physical, etc.):
- Running on WSL2 (Hyper-V backend), on Windows 10 Enterprise, Version 20H2 (OS Build 19042.867)
- WSL2 VM OS: Ubuntu 18.04
- Can't use
docker buildx, as it is an experimental feature, and I run in a production environment.