Update examples using Docker Compose #4857
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
This PR updates the
docker-compose
andevent-driven-architecture
example README files to reflect updated commands and practices, along with minor text adjustments.Details / Rationale
Update to Docker Compose v2 Commands:
docker-compose
command), which has passed its end-of-life. It has now been replaced by the built-indocker compose
subcommands (removing the dash fromdocker-compose
) and eliminatedDocker Compose
as a separate requirement since it is included with Docker.Replace
docker system prune
withdocker compose down
:docker system prune --volumes
to clear the environment. This command has been replaced withdocker compose down --volumes
. The earlier is potentially destructive as it affects all other containers and volumes, not just those related to the Apicurio Registry setup as intended.docker compose down
is safer and the appropriate command for stopping and removing containers, networks, and volumes defined in the Docker Compose file without impacting other Docker resources on the user's system.