Maintaining backwards compatibility with Compose V1 is typically achievable by ensuring that literal values (no Run docker compose config on the project to preview the configuration after Compose V2 has performed interpolation to
env file values contain literal $ signs in them? (This is common with PHP projects!) env file values have escape sequences or nested quotes? Is my project using multiple levels of environment variable overrides (e.g.env file and -env CLI flags)?.env file interpolation and includes numerous examples covering tricky situations such as escaping nested quotes. filter=status=running.Įnvironment variable behavior in Compose V1 was not formally documented and behaved inconsistently in some edge cases.įor Compose V2, the Environment variables section covers both precedence as well as. Only allows filtering by specific properties, e.g. Allows filtering by arbitrary service properties. Uses _ as word separator for container names instead of - to match V1. Migrates YAML fields based on legacy schema version. The following behave differently between Compose V1 and V2:ĭeprecated. docker-compose scale (use docker compose up -scale instead).The following were deprecated in Compose V1 and are not supported in Compose V2: Command-line flags and subcommandsĬompose V2 still supports almost all Compose V1 flags and subcommands, so in most cases, it can be used as a drop-in replacement in scripts. In Compose V2, the global -compatibility flag or COMPOSE_COMPATIBILITY environment variable preserves the Compose V1 behavior to use underscores ( _) as the word separator.Īs this option must be specified for every Compose V2 command run, we recommend only using this as a temporary measure while transitioning to Compose V2. Underscores are not valid characters in DNS hostnames.īy using a hyphen instead, Compose V2 ensures service containers can be accessed over the network via consistent, predictable hostnames.įor example, running the Compose command -p myproject up -scale=1 svc results in a container named myproject_svc_1 with Compose V1 and a container named myproject-svc-1 with Compose V2. In Compose V2, a hyphen ( -) is used as the word separator. In Compose V1, an underscore ( _) was used as the word separator. Service container namesĬompose generates container names based on the project name, service name, and scale/replica count.
#Mac double commander update
Update scripts to use Compose V2 by replacing the hyphen ( -) with a space, using docker compose instead of docker-compose. This change enables using all of the shared flags on the root docker command.įor example, docker -log-level=debug -tls compose up enables debug logging from the Docker Engine as well as ensures that TLS is used for the connection. The Docker CLI platform provides a consistent and predictable set of options and flags, such as the DOCKER_HOST environment variable or the -context command-line flag. Unlike Compose V1, Compose V2 integrates into the Docker CLI platform and the recommended command-line syntax is docker compose. It offers an improved CLI experience, improved build performance with BuildKit, and continued new-feature development.įor most projects, switching to Compose V2 requires no changes to the Compose YAML or your development workflow. What are the functional differences between Compose V1 and Compose V2?Ĭompose V2 introduces a new internal architecture integrated with the rest of the Docker platform. Compose V1 no longer receives updates and will not be available in new releases of Docker Desktop after June 2023.Ĭompose V2 is included with all currently supported versions of Docker Desktop.įor more information, see Migrate to Compose V2.
0 kommentar(er)
