-
Notifications
You must be signed in to change notification settings - Fork 127
Closed
Labels
good first issueGood for newcomersGood for newcomers
Description
I have been testing the elastic-package tool inside of Windows Subsystem for Linux (WSL2) and have used the latest Docker installation that uses Compose V2 which is docker compose. This in turn then does not work with elastic-package as it expects docker-compose
napsta@TESTLL:~$ elastic-package stack up -d -v
2023/06/13 10:43:32 DEBUG Enable verbose logging
Boot up the Elastic stack
Using profile /home/napsta/.elastic-package/profiles/default.
Remember to load stack environment variables using 'eval "$(elastic-package stack shellinit)"'.
Elasticsearch host: https://127.0.0.1:9200
Kibana host: https://127.0.0.1:5601
Username: elastic
Password: changeme
Local package-registry will serve packages from these sources:
- Proxy to https://epr.elastic.co
2023/06/13 10:43:33 DEBUG running command: docker-compose version --short
2023/06/13 10:43:33 ERROR Unable to determine Docker Compose version: running Docker Compose version command failed: exec: "docker-compose": executable file not found in $PATH. Defaulting to 1.x
2023/06/13 10:43:33 DEBUG running command: docker-compose -f /home/napsta/.elastic-package/profiles/default/stack/snapshot.yml -p elastic-package-stack build
Error: booting up the stack failed: building docker images failed: running command failed: running Docker Compose build command failed: exec: "docker-compose": executable file not found in $PATH
Here are the documents to migrating to Compose V2. It seems like V1 (docker-compose) is End of Life June 2023 (this month) which means it will no longer receive updates.
https://docs.docker.com/compose/migrate/
Is this something in the works or being considered?
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomers