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 (or x-aws-protocol) is set to http or https
• 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 format storageaccount/fileshare
• docker compose ls command to list deployed ECS / ACI compose applications
• docker 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 #21)
• Improved output when creating an ACI context

Bug Fixes

• Fixed a bug where ACR Auto-login did not work in some scenarios (cf #29)

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 #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 to stop a container before rm it, or need to specify docker 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 #20

v0.1.10

New features

• Added docker logout azure

Changes

• Removed the single--container--aci container name when doing docker 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 (#16)
• Fixed non-interactive ACI context creation

v0.1.8

New features

• Added docker logout azure

Changes

• Removed the single--container--aci container name when doing docker 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 (#16)
• Fixed non-interactive ACI context creation

v0.1.7

New features

• Add support for following logs with docker logs --follow
• docker run ... will attach to logs by default, you can detach with the --detach flag
• Add support for environment variables (#11)
• Add support for CPU/Memory limits (#7)

Bug fixes

• Login with Azure multi-tenant accounts (#8)
• Bug fixed deploying ACR images on Linux (#10)

v0.1.4

Docker Azure integration for Linux