Unable to build sequentially anymore with docker compose build

[gboer]

Description

Before I had the option to either build sequentially or in parallel by using the --parallel flag for docker-compose build, but now that I've upgraded to Docker Desktop 4.6.1 (Compose version 2.3.3), I can't choose anymore. It always builds in parallel and there's no way to disable it. This is important for me, because of NPM. I'm not entirely sure what they do on their end, but I think they either cannot handle the traffic, or they block traffic when there are too many connections from one IP, because I'm getting a lot network timeouts when I build everything in parallel. Before I was able to just build things sequentially and it would usually go through.

Steps to reproduce the issue:

1. run docker-compose build

Describe the results you received:
It builds all my images in parallel

Describe the results you expected:
Build sequentially, or at least give me the option to disable parallel building.

Output of docker compose version:

Docker Compose version v2.3.3

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.1)
  compose: Docker Compose (Docker Inc., v2.3.3)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 6
  Running: 4
  Paused: 0
  Stopped: 2
 Images: 126
 Server Version: 20.10.13
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 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 logentries splunk syslog
 Swarm: active
  NodeID: g0elf12niwiwuiu1xp2zlu0so
  Is Manager: true
  ClusterID: dnhn74jnbw5mgsl8w3hgbzm0k
  Managers: 1
  Nodes: 1
  Default Address Pool: 10.0.0.0/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: 192.168.65.3
  Manager Addresses:
   192.168.65.3:2377
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 2a1d4dbdb2a1030dc5b01e96fb110a9d9f150ecc
 runc version: v1.0.3-0-gf46b6ba
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 10
 Total Memory: 7.772GiB
 Name: docker-desktop
 ID: V5HQ:MSAT:R2IH:SGNN:2I6Q:ZYVU:A3WJ:CDJ6:M77K:6FHE:2H6U:UQXR
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 96
  Goroutines: 229
  System Time: 2022-04-01T17:35:10.6638264Z
  EventsListeners: 4
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
 Live Restore Enabled: false

Additional environment details:

[ndeloof]

Closing this as a duplicate for #9091