for-win
for-win copied to clipboard
Docker desktop 4.27.2 does not update docker compose.
Description
After upgrading docker desktop to v4.27.2, the docker compose version remains at 2.19.0. The latest Docker Compose is 2.24.6. (desktop 4.27.2 release notes specifies the included compose version should be 2.24.5) The documentation says to upgrade docker compose, install the latest docker desktop.
Is this because there are no windows compatible builds yet? Is there a way to build explicitly for windows myself? (I ask as I need features in v2.22 or higher (docker compose watch))
update
As noted in comments, manually deleting the C:\Users\username\.docker
folder allows successful re-installation with the correct version of compose.
Reproduce
Install Docker Desktop v4.27.2
check version of compose:
docker compose version
Docker Compose version v2.19.0
Expected behavior
Docker Compose version v2.24.5
docker version
Client:
Cloud integration: v1.0.35+desktop.11
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:02 2024
OS/Arch: windows/amd64
Context: default
Server: Docker Desktop 4.28.0 (139021)
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:25 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client:
Version: 25.0.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.0
Path: C:\Users\jprice\.docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.19.0
Path: C:\Users\jprice\.docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.24
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.22
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.0.1
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.5.0
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 9
Running: 0
Paused: 0
Stopped: 9
Images: 20
Server Version: 25.0.3
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
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: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.133.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 2.845GiB
Name: docker-desktop
ID: ed65529d-32a1-44fd-9ab1-90166a60c97b
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
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
AA457EDD-6104-4040-A0B9-8B7D557652A1/20240305223009
Additional Info
No response
edited as upgrading to 4.28 also failed to update compose
Possibly resolved (with manual intervention).
After manually deleting the C:\users\username\.docker
folder and re-installing, compose was updated successfully...
This folder WAS NOT automatically removed when docker desktop was uninstalled. However, it was re-created when I re-installed docker desktop.
Steps taken to resolve:
- Uninstall Docker Desktop
- Cleanup program files folders
- Manually delete the
.docker
folder fromC:\users\username\
folder - Re-install docker desktop 4.27.2
docker version
Client:
Cloud integration: v1.0.35+desktop.10
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:02 2024
OS/Arch: windows/amd64
Context: default
Server: Docker Desktop 4.27.2 (137060)
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:25 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker compose version
Docker Compose version v2.24.5-desktop.1
@doublehelix thank you for the workaround. I had the same issue, and I noticed that when I tried to delete/move the C:\users\username\.docker
folder, I had to close VSCode (which has the Docker extension) before it could be moved. It appears that extension had the folder open. I wonder if that is preventing the update functionality of Docker from changing files there as needed when doing updates. Do you use VSCode with the Docker plugin too?
@doublehelix thank you for the workaround. I had the same issue, and I noticed that when I tried to delete/move the
C:\users\username\.docker
folder, I had to close VSCode (which has the Docker extension) before it could be moved. It appears that extension had the folder open. I wonder if that is preventing the update functionality of Docker from changing files there as needed when doing updates. Do you use VSCode with the Docker plugin too?
Yes, indeed I do. Could very well have been an issue. I'll have to retest with vscode closed (which is rare). Thanks 👍