docker-compose/docs/aci-compose-features.md

Compose - Azure Container Instances mapping

This document outlines the conversion of an application defined in a Compose file to ACI objects. At a high-level, each Compose deployment is mapped to a single ACI container group. Each service is mapped to a container in the container group. The Docker ACI integration provides does not allow scaling of services.

Compose fields mapping

The table below lists supported Compose file fields and their ACI counterparts.

Legend:

• ✓: Implemented
• n: Not yet implemented
• x: Not applicable / no available conversion

Exposing ports

When one or more services expose ports, the entire ACI container group will be exposed and will get a public IP allocated.
As all services are mapped to containers in the same container group, only one service cannot expose a given port number. ACI does not support port mapping, so the source and target ports defined in the Compose file must be the same.

When exposing ports, a service can also specify the service domainname field to set a DNS hostname. domainname will be used to specify the ACI DNS Label Name, and the ACI container group will be reachable at ..azurecontainer.io. All services specifying a domainname must set the same value, as it is applied to the entire container group. domainname must be unique globally in .azurecontainer.io

Persistent volumes

Docker volumes are mapped to Azure file shares. Only the long Compose volume format is supported meaning that volumes must be defined in the volume section. Volumes are defined with a name, the driver field must be set to azure_file, and driver_options must define the storage account and file share to use for the volume. A service can then reference the volume by its name, and specify the target path to be mounted in the container.

services:
    myservice:
        image: nginx
        volumes:
        - mydata:/mount/testvolumes

volumes:
  mydata:
    driver: azure_file
    driver_opts:
      share_name: myfileshare
      storage_account_name: mystorageaccount

The short volume syntax is not allowed for ACI volumes, as it was designed for local path bind mounting when running local containers. A Compose file can define several volumes, with different Azure file shares or storage accounts.

Credentials for storage accounts will be automatically fetched at deployment time using the Azure login to retrieve the storage account key for each storage account used.

Container Resources

CPU and memory reservations and limits can be set in compose. Resource limits must be greater than reservation. In ACI, setting resource limits different from resource reservation will cause containers in the same container group to compete for resources. Resource limits cannot be greater than the total resource reservation for the container group. (Therefore single containers cannot have resoure limits different from resource reservations)

services:
  db:
    image: mysql
    deploy:
      resources:
        reservations:
          cpus: '2'
          memory: 2G
        limits:
          cpus: '3'
          memory: 3G
  web:
    image: nginx
    deploy:
      resources:
        reservations:
          cpus: '1.5'
          memory: 1.5G

In this example, the db container will be allocated 2 CPUs and 2G of memory. It will be allowed to use up to 3 CPUs and 3G of memory, using some of the resources allocated to the web container. The web container will have its limits set to the same values as reservations, by default.

© 2025 Gogs

Page: 237ms Template: 27ms

English

English 简体中文 繁體中文（香港） 繁體中文（臺灣） Deutsch français Nederlands latviešu русский 日本語 español português do Brasil polski български italiano suomi Türkçe čeština српски svenska 한국어 galego українська English (United Kingdom) Magyar Slovenčina Indonesian Persian Vietnamese Português Монгол Română

Javascript Licenses Website

Keys	Map	Notes
Service	✓
service.service.build	x	Ignored. No image build support on ACI.
service.cap_add, cap_drop	x
service.command	✓	Override container Command. On ACI, specifying command will override the image command and entrypoint, if the image has an command or entrypoint defined
service.configs	x
service.cgroup_parent	x
service.container_name	x	Service name is used as container name on ACI.
service.credential_spec	x
service.deploy	✓
service.deploy.endpoint_mode	x
service.deploy.mode	x
service.deploy.replicas	x	Only one replica is started for each service.
service.deploy.placement	x
service.deploy.update_config	x
service.deploy.resources	✓	Restriction: ACI resource limits cannot be greater than the sum of resource reservations for all containers in the container group. Using container limits that are greater than container reservations will cause containers in the same container group to compete with resources.
service.deploy.restart_policy	✓	One of: any, none, on-failure. Restriction: All services must have the same restart policy. The entire ACI container group will be restarted if needed.
service.deploy.labels	x	ACI does not have container-level labels.
service.devices	x
service.depends_on	x
service.dns	x
service.dns_search	x
service.domainname	✓	Mapped to ACI DNSLabelName. Restriction: all services must specify the same domainname, if specified. domainname must be unique globally in .azurecontainer.io
service.tmpfs	x
service.entrypoint	x	ACI only supports overriding the container command.
service.env_file	✓
service.environment	✓
service.expose	x
service.extends	x
service.external_links	x
service.extra_hosts	x
service.group_add	x
service.healthcheck	n
service.hostname	x
service.image	✓	Private images will be accessible if the user is logged into the corresponding registry at deploy time. Users will be automatically logged in to Azure Container Registry using their Azure login if possible.
service.isolation	x
service.labels	x	ACI does not have container-level labels.
service.links	x
service.logging	x
service.network_mode	x
service.networks	x	Communication between services is implemented by defining mapping for each service in the shared /etc/hosts file of the container group. Each service can resolve names for other services and the resulting network calls will be redirected to localhost.
service.pid	x
service.ports	✓	Only symetrical por mapping is supported in ACI. See #exposing-ports.
service.secrets	✓
service.security_opt	x
service.stop_grace_period	x
service.stop_signal	x
service.sysctls	x
service.ulimits	x
service.userns_mode	x
service.volumes	✓	Mapped to AZure File Shares. See #persistent-volumes.
service.restart	x	Replaced by service.deployment.restart_policy
Volume	x
driver	✓	See #persistent-volumes.
driver_opts	✓
external	x
labels	x
Secret	x
TBD	x
Config	x
TBD	x