enow.com Web Search

Search results

  1. Results from the WOW.Com Content Network
  2. Docker-compose.yml: `version` is obsolete - Docker Hub - Docker...

    forums.docker.com/t/docker-compose-yml-version-is-obsolete/141313

    I just updated docker desktop and docker-compose to version v2.27.0-desktop.2 and i cant use version: 3.8 in the docker file anymore

  3. According to the docker issue 11628 (docker/compose#11628) the 'version' field in docker-compose files is outdated.

  4. It looks like your version of docker-compose is incompatible. The version you are using (1.17.1) only supports a compose file format up to version 3.4. You can view the compatibility matrix in the release notes: 1.17.1 release. You can update docker-compose with the following:

  5. Do you still use version in Docker compose? - DEV Community

    dev.to/ajeetraina/do-we-still-use-version-in-compose-3inp

    While the version property might have been essential in the past, it's no longer necessary in modern Docker Compose workflows. By removing it, you can simplify your Compose files and stay up-to-date with the latest features.

  6. The end of Docker-Compose - Medium

    medium.com/@jerome.devops/the-end-of-docker-compose-e3b7d15330e2

    TL;DR: The version attribute in Docker Compose is now obsolete in V2. Remove it from your docker-compose.yml file to avoid warnings.

  7. How to upgrade docker-compose to latest version

    stackoverflow.com/questions/49839028

    Docker compose V2 was rewritten from Python to Go, and thus this answer here is obsolete and no longer works. If you tried sudo apt-get remove docker-compose and get E: Unable to locate package docker-compose, try this method : This command must return a result, in order to check it is installed here : Remove the old version :

  8. Version and name top-level elements | Docker Docs

    docs.docker.com/reference/compose-file/version-and-name

    Version top-level element (obsolete) The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative and you'll receive a warning message that it is obsolete if used.

  9. ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.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.

  10. Docker has deprecated the use of version in the root level of the docker compose yaml beginning with Docker Compose 1.27+. The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative.

  11. TIL that you declaring version in docker-compose has been ... - ...

    www.reddit.com/.../comments/ny4syf/til_that_you_declaring_version_in_dockercompose

    Update in 2021: The new Docker Compose spec supports not defining a version property and is the recommended way to go moving forward. It supports both v2 and v3 properties. The Compose file is a YAML file defining version (DEPRECATED), services (REQUIRED), networks, volumes, configs and secrets.