Technical questionAccepted answer
Is there a way to increase the log size in docker when building a container?
alphabet5
Jan 21
0 views1
In the output when building, I am getting this message:
[output clipped, log limit 1MiB reached]
from the command
docker build --progress plain .
The current workaround I have is to pipe larger sections of the RUN command in the dockerfile to /dev/null i.e.
RUN \
echo "**** install packages ****" && \
apt-get update && \
apt-get install -y libcairo2-dev libjpeg-turbo8-dev libpng-dev libtool-bin libossp-uuid-dev wget maven default-jdk > /dev/null
docker1 answer
Accepted answer · original discussion
alphabet5
PermalinkJan 23
With the key link provided by @Luke Deluccia, this is what worked for me.
docker buildx create --use --name larger_log --driver-opt env.BUILDKIT_STEP_LOG_MAX_SIZE=50000000
docker buildx build --progress plain .
This creates a buildx instance, and sets buildx to use the instance when building. This did not clip the logs during the build process.
1 question comment
Use comments to ask for clarification. Post a solution as an answer.
Luke DeLucciaPermalink
Jan 22
I was able to get around this issue by creating a builder with
docker buildx create --driver-opt env.BUILDKIT_STEP_LOG_MAX_SIZE=50000000 and then using the builder with docker buildx build, but have not been able to fix the issue when using the default builder and docker build.