docker / docker/docker-py

Question: What is the equivalent in docker-py to "--progress=plain" or BUILDKIT_PROGRESS=plain?

Open
#3,347 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.2k
Forks
1.7k
Avg merge
13d 8h
Merged PRs (30d)
2

Description

I need to debug the cause of a build failure using docker-py when building from a dockerfile that was created dynamically within python.

For example, the error I'm getting is:

...
Step 4/14 : RUN pip install uv
Step 5/14 : COPY .requirements .
Step 6/14 : RUN uv pip install --no-cache-dir -r .requirements
...
RuntimeError: Docker error: The command '/bin/sh -c uv pip install --no-cache-dir -r .requirements' returned a non-zero code: 1.

The docker daemon logs (with debug=true in daemon.json) doesn't show anything obvious.

If using the CLI, we can add docker build --progress=plain ... or use export BUILDKIT_PROGRESS=plain to show the details.

However, I want to do this within docker-py and it's not obvious how to do this looking at the docs.

Is there a way to enable the equivalent of "--progress=plain"| " BUILDKIT_PROGRESS=plain" in docker-py?

Thanks for any suggestions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the docker-py build API and Docker Engine API behavior with the CLI options --progress=plain and BUILDKIT_PROGRESS=plain. Check whether the documented Python interface exposes an equivalent setting and identify the relevant documentation entry point; done means the supported approach, or its absence and limitation, is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
devops
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.