This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Releases: docker-archive/compose-cli
Releases · docker-archive/compose-cli
v0.1.16
New
- Introduced support for external EFS volumes
Bug fixes
- fixed regression when setting HOME to empty string, see docker/for-mac#4919
v0.1.15
New
- ECS simulation mode: users can now create an ECS simulation context to run local applications using AWS services.
- ECS integration creates an Application Load Balancer if
protocol
(orx-aws-protocol
) is set tohttp
orhttps
- ACI volume management: users can use docker commands to create, list and remove volumes on Azure, in order to use these volumes in containers and compose applications.
Volume references when running ACI containers are now in the formatstorageaccount/fileshare
docker compose ls
command to list deployed ECS / ACI compose applicationsdocker compose ps
command to list services of a compose application in ACI (already available in ECS contexts)
Bug Fixes
- Fixed a bug in Azure login on some WSL2 configurations. Now falling back to Azure device code flow.
- ACI: Stop following logs when the container gets stopped
- ACI: properly pass environment variables using
docker run -e key=value
, when value includes "=" - ECS: properly set TaskRole according to configured managed policies/IAM role
v0.1.14
New
- ECS integration : users can now also create an ECS context and deploy a compose application on ECS doing
docker compose up
. See https://docs.docker.com/engine/context/ecs-integration/ for details
Improvements
- ACR auto-login now works including when logging in with an Azure Service Provider (cf docker-archive/cloud-integration-beta#21)
- Improved output when creating an ACI context
Bug Fixes
- Fixed a bug where ACR Auto-login did not work in some scenarios (cf docker-archive/cloud-integration-beta#29)
v0.1.13
Merge pull request #533 from docker/more_ecs_e2e More ECS E2E tests (secrets), in // of compose
v0.1.12
New
- Auto-login to ACR repository from Azure login, when deploying ACR images
- Auto-login to Azure storage account from Azure login, when using Azure File Share in ACI volumes
- Ability to provide service principal client id & secret in
docker login azure
command (limitation : no refresh token is provided with Service Principal login, user must manually re-login). See docker-archive/cloud-integration-beta#21 - Ability to docker stop/start single containers (not supported in compose applications).
docker rm
is now more inline with the local experience : users need tostop
a container beforerm
it, or need to specifydocker rm --force
(-f) to force removal- Fix docker ps output that was displaying stopped containers even if
--all
was not specified - Ability to specify restart policy for single containers, or compose application, as long as the same policy is applied to all containers in the app
docker login azure
web page now redirects to https://docs.docker.com/engine/context/aci-integration/- Explicit error message when users try to specify labels in compose file, not supported in docker ACI integration
Bugfixes
- bugfix propagating process signals to containers. See docker/cli#2653
- bug fix in WSL2 azure login. See docker-archive/cloud-integration-beta#20
v0.1.12-alpha1
Merge pull request #473 from docker/fix_warn_forward_signal Do not display warning if cannot forward signal to child.
v0.1.11
Merge pull request #471 from docker/fix-run-timeout Put 40 seconds for timeout instead of 20
v0.1.10
New features
- Added
docker logout azure
Changes
- Removed the
single--container--aci
container name when doingdocker run
, the name of the container is the random-generated name we all know and love
Bug fixes
- Fixed non-interactive exec (you can
docker exec <CONTAINER> ls
on an ACI context now) - Fixed
docker logs --follow
on Windows (docker-archive/cloud-integration-beta#16) - Fixed non-interactive ACI context creation
v0.1.9
v0.1.8
- Fixed non-interactive exec (you can
docker exec <CONTAINER> ls
on an ACI context now) - Added
docker logout azure
- Removed the
single--container--aci
container name when doingdocker run
, the name of the container is the random-generated name we all know and love - Fixed
docker logs --follow
on Windows (docker-archive/cloud-integration-beta#16) - Fixed non-interactive ACI context creation (https://github.com/docker/desktop-microsoft/issues/40)
- Added the platform when doing an inspect with node-sdk, need to use the master branch of
node-sdk
since we didn't make a new release of it yet