zrhoffman opened a new issue, #8055: URL: https://github.com/apache/trafficcontrol/issues/8055
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at secur...@trafficcontrol.apache.org and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to users-subscr...@trafficcontrol.apache.org to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Bug Report affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Control Cache Config (`t3c`, formerly ORT) - Traffic Control Health Client (t3c-health-client) - Traffic Monitor - Traffic Ops - Traffic Portal - Documentation - CDN in a Box - Automation <!-- Please specify which (GitHub Actions, Docker images, Ansible Roles, etc.) --> ## What did you do? <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> `./pkg -v cache-config_build` ## What did you expect to happen? <!-- Describe how the bug happens --> `cache-config` successfully builds. ## What actually happened? <!-- Describe what the behavior would be without the bug --> ```shell + ./pkg -v cache-config_build Version in "././infrastructure/docker/build/docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version ("2.0", "2.1", "3.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/ Building cache-config_build. Version in "././infrastructure/docker/build/docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version ("2.0", "2.1", "3.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/ Failed to build cache-config_build. ``` Reason: The `version` key in `docker-compose.yml` has been deprecated for awhile now, but now using it with compose file version 3.8 is explicitly an error. The `version` key should be removed completely. And, to ensure that only recent docker compose versions are used, which ensures that they will support this change, instances of `docker-compose` should be changed to `docker compose`. If an old `docker-compose` version is used with the `version` key removed from the compose file, it will complain about unknown keys in the compose file, because it will assume that compose file version 1 is used. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@trafficcontrol.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
