Implement a mechanism to define docker images to pull #28
Conversation
This file contains 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
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.
Decription
Implement a mechanism to define docker images to pull. This is defined in configuration file "scripts/config.hcl", which is a list of images separated by comma
common_custom_docker_images = "<image1>,<image2>"For example, if you want pull image "hello-world:latest" and image "alpine:latest" in this OVF. You can define it as followed:
common_custom_docker_images = "hello-world:latest,alpine:latest"Test
Use the following configuration:
common_custom_docker_images = "hello-world:latest,alpine:latest"A frozen VM are generated successfully.
A ray cluster are provisioned successfully with this frozen VM .
Check the head node, which is containing docker images as expected:
