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
I'm not sure whether we want to check for docker-compose then docker compose or just switch straight over to the new method. Beyond the change in the name of the command, they have seemed the same, but I haven't really compared explicitly.
Ideally this would try docker compose first, if spawn throws a command not found error (test to see what this is), then try the old way docker-compose, if both fail then tell the user they need to install docker compose.
- Updated docker-compose-js package to use `docker compose` by default
instead of `docker-compose`
- This is because Compose V1 won’t be supported anymore and will be
removed from all Docker Desktop versions.
- NOTE: `docker-compose` is still backwards compatible if `docker
compose` is not present.
- Bump **packages/docker-compose-js** from `v1.3.1` to `v1.3.2`
- Added user feedback in the event that `docker-compose` or `docker
compose` is not installed.
ref to issue #3350
The
docker-compose
command has been deprecated and is being removed and replaced withdocker compose
.https://docs.docker.com/compose/#compose-v2-and-the-new-docker-compose-command
I'm not sure whether we want to check for
docker-compose
thendocker compose
or just switch straight over to the new method. Beyond the change in the name of the command, they have seemed the same, but I haven't really compared explicitly.https://github.com/terascope/teraslice/blob/master/packages/docker-compose-js/src/index.ts#L65
The text was updated successfully, but these errors were encountered: