Is there a way to change BUILDKIT_STEP_LOG_MAX_SIZE and BUILDKIT_STEP_LOG_MAX_SPEED variables?

[Noksa]

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

Expected behavior

I want to disable output clipped, log limit 1MiB reached behaviour and want to see the entire log instead of small part.

Actual behavior

I can't find a way how to do that.

On linux we can adjuest those variables in docker systemd service

Information

• macOS Version: 12.4
• Intel chip or Apple chip: Apple
• Docker Desktop Version: 4.8.2 (79419)

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

❯ ~ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0017: can a VM be started?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0019: is the com.docker.vmnetd process responding?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.

Steps to reproduce the behavior

1. Run docker build . using the following Dockerfile and you will receive [output clipped, log limit 100KiB/s reached]

# syntax=docker/dockerfile:1.4
FROM bash
RUN <<eot
  trap 'exit 0' SIGINT SIGTERM ERROR
  while true; do
    yes "HelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorld" | head -n 100
  done
eot

2. Run docker build . using the following Dockerfile and you will receive [output clipped, log limit 1MiB reached] after ~20 seconds

# syntax=docker/dockerfile:1.4
FROM bash
RUN <<eot
  trap 'exit 0' SIGINT SIGTERM ERROR
  while true; do
    yes "HelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorld" | head -n 100
    sleep 0.1
  done
eot

[MichaelVoelkel]

Really? No answer? Even for a relatively small docker file this stupid log clipping (who asked for this?) immediately makes problems. And it's hard to google an answer for this and, if you find anything, it's setting this option which apparently is not available on macOS?!

[JohnPremKumar]

Facing the Same issue on my M1 Mac. Did anyone find any solution for changing this behavior on MacOS? Currently disabling buildkit seems to be the only solution to avoid this issue.

[chloe-zen]

Ditto. Odd that there's no response on a basic question like this.

PING

[lkalina-cera]

I tried

export BUILDKIT_STEP_LOG_MAX_SPEED=10240000
export BUILDKIT_STEP_LOG_MAX_SIZE=1073741824

from mac os shell before docker build and it looks like working.

[maciek16180]

Any hopes for an answer? We are using docker in GitLab CI and simple exporting variables seems to have no effect there.

[brentkearney]

This is still an issue on Apple M1, MacOS 12.6 (21G115) with Docker Desktop 4.12.0 (85629).

#0 1061.7 [output clipped, log limit 1MiB reached]
------
failed to solve: executor failed running [/bin/sh -c bundle install -j4 --retry=3]: exit code: 5

[jiangyixiang]

any solution?

[clemsos]

I got tests failing on CI with only a clipped log to debug it, which makes me very sad. Any update or workaround to make it work with compose?

#31 76.76 [output clipped, log limit 1MiB reached]
#31 ERROR: executor failed running [/bin/sh -c yarn install]: exit code: 1

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[Noksa]

Up. Still the issue. We are going to celebrate 1 year anniversary soon!

[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.

/lifecycle locked