Description
The newly (2.39) added feature --provenance of docker compose build doesn't seem to work on Docker desktop mac.
Docs says it should work:
- In compose file reference, add a
service>build>provenance field https://docs.docker.com/reference/compose-file/build/#provenance
- In CLI like this https://docs.docker.com/reference/cli/docker/compose/build/
docker compose build --provenance false my-service
It works as expected in ubuntu. Unfortunately on mac, when pushing the image to ECR, I still get the multi-platform issue (described here).
Note that, running with docker buildx works fine and doesn't lead to the issue docker buildx build --platform=linux/amd64 --provenance=false .
Steps To Reproduce
Using this compose.yaml
services:
my-service:
image: my-service:local
build:
context: ./service
provenance: false
platforms:
- linux/amd64
tags:
- AWS_ACCOUNT_ID.dkr.ecr.REGION.amazonaws.com/my-service:${VERSION:-latest}
platform: linux/amd64Note that I tested with false as string or yaml boolean.
And then then build and pushing to ECR you still get the provenance.
docker compose build
docker push AWS_ACCOUNT_ID.dkr.ecr.REGION.amazonaws.com/my-service:${VERSION:-latest}
Running with
docker compose build --provenance false
Also causes the same issue.
Compose Version
Docker Compose version v2.39.1-desktop.1
Docker Environment
Client:
Version: 28.3.2
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.9.11
Path: /Users/gee/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.26.1-desktop.1
Path: /Users/gee/.docker/cli-plugins/docker-buildx
cloud: Docker Cloud (Docker Inc.)
Version: v0.4.11
Path: /Users/gee/.docker/cli-plugins/docker-cloud
compose: Docker Compose (Docker Inc.)
Version: v2.39.1-desktop.1
Path: /Users/gee/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.42
Path: /Users/gee/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.2.0
Path: /Users/gee/.docker/cli-plugins/docker-desktop
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.29
Path: /Users/gee/.docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/gee/.docker/cli-plugins/docker-init
mcp: Docker MCP Plugin (Docker Inc.)
Version: v0.13.0
Path: /Users/gee/.docker/cli-plugins/docker-mcp
model: Docker Model Runner (EXPERIMENTAL) (Docker Inc.)
Version: v0.1.36
Path: /Users/gee/.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/gee/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.18.2
Path: /Users/gee/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/gee/.docker/cli-plugins/docker-dev" is not valid: failed to fetch metadata: fork/exec /Users/gee/.docker/cli-plugins/docker-dev: no such file or directory
WARNING: Plugin "/Users/gee/.docker/cli-plugins/docker-feedback" is not valid: failed to fetch metadata: fork/exec /Users/gee/.docker/cli-plugins/docker-feedback: no such file or directory
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 12
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: 9f015255-6998-4d94-b15c-772c4b7b8213
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/gee/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
Anything else?
No response
Description
The newly (2.39) added feature
--provenanceof docker compose build doesn't seem to work on Docker desktop mac.Docs says it should work:
service>build>provenancefield https://docs.docker.com/reference/compose-file/build/#provenancedocker compose build --provenance false my-serviceIt works as expected in ubuntu. Unfortunately on mac, when pushing the image to ECR, I still get the multi-platform issue (described here).
Note that, running with docker buildx works fine and doesn't lead to the issue
docker buildx build --platform=linux/amd64 --provenance=false .Steps To Reproduce
Using this compose.yaml
Note that I tested with
falseas string or yaml boolean.And then then build and pushing to ECR you still get the provenance.
Running with
Also causes the same issue.
Compose Version
Docker Environment
Anything else?
No response