This wasn't me who reported, but I got this error on he most up to date compose file.
After a quick look, the machine I was trying to run it on was running an old version of docker, and was using docker compose v1 instead of 2.
Updating the compose version to v2 addressed this issue.