Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: image load #2102

Closed
wants to merge 3 commits into from
Closed

feat: image load #2102

wants to merge 3 commits into from

Conversation

lostbean
Copy link
Contributor

Description:

Load container images directly into Kurtosis.

Is this change user facing?

NO

ImagerRegistrySpec *image_registry_spec.ImageRegistrySpec
// Reference to a image file that can be loaded into a backend image
// This is one of the options to reference a image and this value is optional (i.e. nil)
ImageLoad *image_load.ImageLoad
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a usecase for this? I'd imagine users would be either a) specifying an existing Docker image, or b) getting an image through indirect means (either ImageBuildSpec or NixBuildSpec)

LoadImageAttr = "image_file_path"
)

func NewImageLoadType() *kurtosis_type_constructor.KurtosisTypeConstructor {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question as above - makes a lot of sense to me that a KurtosisBackend needs the ability to load images, but do we expect users to be writing Starlark that references an image .tgz?

@lostbean
Copy link
Contributor Author

lostbean commented Feb 7, 2024

deprecated in favor of Nix builds: #2132

@lostbean lostbean closed this Feb 7, 2024
@lostbean lostbean deleted the edgar/image_load branch February 7, 2024 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants