You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently stated minimal version of docker-compose
The minimum version of docker-compose is currently stated at 1.18.0. This number was originally chosen as that is when configuration version 3.5 was introduced and users of Ubuntu 18.04 were being tripped up since apt-get by default will install a version of docker-compose which is older than that.
Upcoming stated minimal version of docker-compose
The plan is to raise the minimum version of docker-compose to 1.25.0 or greater. This version is fairly recent, and default installations of Docker Desktop on Mac OS, Ubuntu 20.04, and Fedora 31 would all meet this requirement (see below table). Users with systems running older versions will require installing current/latest release of docker-compose from published binaries:
Given that Ubuntu 18.04 already requires installing a newer version than is available via repositories, and CentOS 7 appears to be the only recent OS version which would be affected by this move, setting the minimal version of docker-compose to 1.25.0 or greater seems to make the most sense.
Default versions of docker-compose by Operating System
System
Version
Notes
MacOS
1.25.5
Latest Docker Desktop includes 1.25.5; Docker Desktop 2.2.0.0 (minimum required version) includes version 1.25.2
CentOS 7
1.18.0
Available via epel-release repository.
CentOS 8
n/a
Not currently available via repositories.
Fedora 31
1.25.4
Available via docker-ce repository.
Ubuntu 18.04
1.17.1
Available via default repositories.
Ubuntu 20.04
1.25.0
Available via default repositories.
Problems this solves
This solves general issues with inconsistencies resulting from individuals using outdated versions of docker-compose. Development of docker-compose moves fast, and various versions of docker-compose between 1.18 and 1.25 have changed how basic flags such as --project-directory function. With 1.23.1 (and prior) for example, warden env config will fail to correctly output the rendered docker compose configuration, and with 1.23.0 and loading of the .env file may not always work correctly.
Another example of a feature we cannot use currently is the --env-file flag added in 1.25.0 as noted in #131
The text was updated successfully, but these errors were encountered:
warden
gets me this error :
ERROR: docker-compose version should be 1.25.0 or higher ( installed)
My docker-composer :
Docker Compose version v2.0.0-beta.6
This command fixes the issue:
docker-compose disable-v2
Currently stated minimal version of docker-compose
The minimum version of docker-compose is currently stated at 1.18.0. This number was originally chosen as that is when configuration version 3.5 was introduced and users of Ubuntu 18.04 were being tripped up since
apt-get
by default will install a version of docker-compose which is older than that.Upcoming stated minimal version of docker-compose
The plan is to raise the minimum version of docker-compose to 1.25.0 or greater. This version is fairly recent, and default installations of Docker Desktop on Mac OS, Ubuntu 20.04, and Fedora 31 would all meet this requirement (see below table). Users with systems running older versions will require installing current/latest release of docker-compose from published binaries:
Given that Ubuntu 18.04 already requires installing a newer version than is available via repositories, and CentOS 7 appears to be the only recent OS version which would be affected by this move, setting the minimal version of docker-compose to 1.25.0 or greater seems to make the most sense.
Default versions of docker-compose by Operating System
Problems this solves
This solves general issues with inconsistencies resulting from individuals using outdated versions of docker-compose. Development of docker-compose moves fast, and various versions of docker-compose between 1.18 and 1.25 have changed how basic flags such as
--project-directory
function. With 1.23.1 (and prior) for example,warden env config
will fail to correctly output the rendered docker compose configuration, and with 1.23.0 and loading of the.env
file may not always work correctly.Another example of a feature we cannot use currently is the
--env-file
flag added in 1.25.0 as noted in #131The text was updated successfully, but these errors were encountered: