The change can currently be turned off by including the -compatibility flag with docker compose commands. This could break scripts which expect the old container name format to be used. This means a service called db within the app project will now create a container called app-db, instead of app_db. Containers are now created with hyphens in their names instead of underscores.While most migrations should be straightforward, Compose v2 does introduce a few breaking changes which could impact specific use cases: If you have your own tooling around the docker-compose command, you can change it to call docker compose instead. You don’t need to modify your docker-compose.yml files or learn new commands, except for the change from docker-compose to docker compose. This allows Compose to reuse code from the main Docker CLI, creating more consistent behavior.Ĭompose v2 is compatible with v1 in almost all use cases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |