Fix mirage boot api container - #872
Merged
Merged
Conversation
badrogger
approved these changes
Jun 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request refactors service definitions in
node_cli/utils/docker_utils.pyto simplify and consolidate the service composition logic. The most important change is the removal ofCORE_MIRAGE_COMPOSE_SERVICESand its integration into other service groups.Refactoring service definitions:
CORE_MIRAGE_COMPOSE_SERVICESand directly integrated its services intoBASE_MIRAGE_COMPOSE_SERVICESandBASE_MIRAGE_BOOT_COMPOSE_SERVICESto streamline service composition.mirage-boot-apitoBASE_MIRAGE_BOOT_COMPOSE_SERVICESand ensured all service groups consistently inherit fromCORE_COMMON_COMPOSE_SERVICES.