feat: custom builder registry configuration #660
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.
Custom Builder Registry Configuration
Description
This PR introduces the option to choose a custom builder registry that was added to Daytona with
daytona cr set
. The registry will be used to store build images. Additionally, theBuild Image Namespace
option was introduced that is used when tagging and pushing build images.BREAKING CHANGE
Before starting the server, users will need to add 'localBuilderRegistryPort' and 'builderRegistryServer' properties to their server configuration.
The following properties should be added:
(Note:
"registryPort"
can be removed from the config file)Related Issue(s)
Closes #635