Validating error "(root) must be a mapping" after update the docker and docker-compose

deimi86 · January 22, 2024, 1:11pm

It seems that a fix is on the way

github.com/docker/compose

[BUG] "(root) must be a mapping" since 2.4.1

opened 08:19AM - 22 Jan 24 UTC

closed 10:55AM - 22 Jan 24 UTC

ulrichSchreiner

kind/bug

### Description hi, i use vscode with remote containers. since 2.4.1 i get t…he following error (`(root) must be a mapping`), when vscode tries to build my remote container via `docker-compose`: ~~~sh ❯ docker-compose --project-name vscode -f /home/usc/.config/vscode/development.yml -f /home/usc/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1705311452770.yml -f /home/usc/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.containerFeatures-1705311453367.yml up -d --no-recreate validating /home/usc/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1705311452770.yml: (root) must be a mapping ~~~ the problematic file looks like this ~~~yaml version: '3' services: go-development: build: dockerfile: /tmp/devcontainercli-usc/container-features/0.54.1-1705311452768/Dockerfile-with-features args: - BUILDKIT_INLINE_CACHE=1 - _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label ~~~ when i change the args to a mapping like this ~~~yaml args: BUILDKIT_INLINE_CACHE: 1 _DEV_CONTAINERS_BASE_IMAGE: dev_container_auto_added_stage_label ~~~ it works. but the file is generated by vscocde and so i cannot use this workaround. ### Steps To Reproduce Use docker-compose to build an image with an overlay file where build-args are overridden as a list and not as a map. ### Compose Version ```Text ❯ docker-compose --version Docker Compose version 2.24.1 ``` ### Docker Environment ```Text Client: Version: 24.0.7 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: 0.12.1 Path: /usr/lib/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: 2.24.1 Path: /usr/lib/docker/cli-plugins/docker-compose Server: Containers: 3 Running: 3 Paused: 0 Stopped: 0 Images: 1950 Server Version: 24.0.7 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 logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 71909c1814c544ac47ab91d2e8b84718e517bb99.m runc version: init version: de40ad0 Security Options: seccomp Profile: builtin cgroupns Kernel Version: 6.7.0-arch3-1 Operating System: Arch Linux OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 62.5GiB Name: usc-tux15 ID: TY7Y:MYLF:VXR5:O2NM:3NH4:E5XH:BMJD:SWDE:C7HU:SYUO:U33R:7LZM Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ``` ### Anything else? _No response_

A temporary solution is to downgrade your docker-compose-plugin package below 2.24.1