Repository navigation
[BUG] Builds triggered by watch:rebuild triggers fail when filtering log output #13072
Description
Description
Ever since a recent Docker Desktop update on MacOS, I've had to stop filtering the output of my docker compose up --watch because I get this if I'm piping the logs through grep and I make a change that triggers a rebuild:
⦿ Rebuilding service(s) ["multitenant" "multitenant_www"] after changes were detected...
WARN[0418] Error handling changed files: failed to get console: provided file is not a console
⦿ Build failed. Error: failed to get console: provided file is not a console
Steps To Reproduce
- Use a
developstanza in docker-compose.yml that has awatchwith anaction: rebuildtrigger. - Run
docker compose up --watch | grep "some spammy string you don't want to see in your logs" - Update the file referenced in the rebuild trigger.
- Build fails with above error message.
Compose Version
$ docker compose version
Docker Compose version v2.38.2-desktop.1
$ docker-compose version
Docker Compose version v2.38.2-desktop.1
Docker Environment
$ docker info
Client:
Version: 28.3.2
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.8.0
Path: /Users/rrollins/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.25.0-desktop.1
Path: /Users/rrollins/.docker/cli-plugins/docker-buildx
cloud: Docker Cloud (Docker Inc.)
Version: v0.4.2
Path: /Users/rrollins/.docker/cli-plugins/docker-cloud
compose: Docker Compose (Docker Inc.)
Version: v2.38.2-desktop.1
Path: /Users/rrollins/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.41
Path: /Users/rrollins/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.1.11
Path: /Users/rrollins/.docker/cli-plugins/docker-desktop
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.29
Path: /Users/rrollins/.docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/rrollins/.docker/cli-plugins/docker-init
mcp: Docker MCP Plugin (Docker Inc.)
Version: v0.9.9
Path: /Users/rrollins/.docker/cli-plugins/docker-mcp
model: Docker Model Runner (EXPERIMENTAL) (Docker Inc.)
Version: v0.1.33
Path: /Users/rrollins/.docker/cli-plugins/docker-model
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/rrollins/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.18.1
Path: /Users/rrollins/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/rrollins/.docker/cli-plugins/docker-dev" is not valid: failed to fetch metadata: fork/exec /Users/rrollins/.docker/cli-plugins/docker-dev: no such file or directory
Server:
Containers: 6
Running: 6
Paused: 0
Stopped: 0
Images: 7
Server Version: 28.3.2
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Discovered Devices:
cdi: docker.com/gpu=webgpu
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
runc version: v1.2.5-0-g59923ef
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.10.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 12
Total Memory: 7.653GiB
Name: docker-desktop
ID: 42077820-6f80-461d-86a1-c7cb9ef0c903
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/rrollins/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
::1/128
127.0.0.0/8
Live Restore Enabled: false
WARNING: DOCKER_INSECURE_NO_IPTABLES_RAW is set
Anything else?
This started happening around the same time that my previous bug report, #13044, started happening. Given that they're both about the rebuild action while using docker compose up --watch, maybe they're related?
Activity
coredumperror commentedon Jul 18, 2025
Ah ha! I figured it out. Turns out the issue is that I was actually using
docker compose --ansi=always up --watch.I've been using
--ansi=alwaysfor a while because I want docker compose to output ANSI color codes even when I'm piping the output through grep. And that worked fine for years, but now therebuildtrigger cares about the output not being a console.Would it be possible to change that back to how it used to behave?