Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Overlapping print rows while building #12370

Open
MattiasOz opened this issue Dec 10, 2024 · 2 comments
Open

[BUG] Overlapping print rows while building #12370

MattiasOz opened this issue Dec 10, 2024 · 2 comments

Comments

@MattiasOz
Copy link

Description

When docker-compose is building images the printout seems to be confused about which rows to use. It prints out, e.g., both a Dockerfile instruction, like COPY, as well as the current container status on the same row. This results in a constant switching between what is written.

Steps To Reproduce

  1. Enter a directory with a docker-compose.yml file
  2. Run docker-compose build --no-cache

Compose Version

`docker compose version`:
`Docker Compose version 2.31.0`

`docker-compose version`:
`Docker Compose version 2.31.0`

Docker Environment

Client:
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  2.31.0
    Path:     /usr/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 4
  Running: 3
  Paused: 0
  Stopped: 1
 Images: 978
 Server Version: 27.3.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 207ad711eabd375a01713109a8a197d197ff6542.m
 runc version: 
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.6.63-1-MANJARO
 Operating System: Manjaro Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 13.34GiB
 Name: Saturn
 ID: e1c30eb4-300f-4d4d-97d4-2cdbd78aeca8
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Anything else?

I don't really know what caused it to happen. I know the steps to reproduce aren't satisfactory but I'm not sure what else to write. Any insight regarding the printout is appreciated.
Here's an image as well as a video of the building process.
Image
https://github.com/user-attachments/assets/4a0d560c-3ce1-4192-ae2d-533789d41b45
Running with --progress plain works of course but that's sidestepping the issue.
I tried reinstalling. Neither different terminals nor tty changed anything.
P.S. build specifically doesn't have to be run, anything that would cause that specific progress type to display works.

@MattiasOz MattiasOz changed the title [BUG] Overlapping rows [BUG] Overlapping print rows while building Dec 10, 2024
@MattiasOz
Copy link
Author

Update: I works fine after downgrading to earlier versions of docker-compose, for example 2.30.3.

@ndeloof
Copy link
Contributor

ndeloof commented Dec 10, 2024

I also noticed this issue. Seems we need to disable compose progress UI while buildkit is using the console to render build state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants