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

[FEATURE] Create a SOCI Index without a Container Runtime #1057

Open
ollypom opened this issue Jan 30, 2024 · 1 comment
Open

[FEATURE] Create a SOCI Index without a Container Runtime #1057

ollypom opened this issue Jan 30, 2024 · 1 comment
Labels
feature New feature or request

Comments

@ollypom
Copy link

ollypom commented Jan 30, 2024

Description

Today the soci create command can only create a SOCI index from a container image that is stored locally to the soci client in a containerd image store.

client, ctx, cancel, err := internal.NewClient(cliContext)
if err != nil {
return err
}
defer cancel()
cs := client.ContentStore()
is := client.ImageService()
srcImg, err := is.Get(ctx, srcRef)
if err != nil {
return err
}

However the SOCI Index Builder is able to generate a SOCI Index by first downloading and extracting a container image to a local arbitrary directory on the host using the ORAS library. Then it imports the logic from this repository to create the SOCI Index. Showing that its possible to generate a SOCI Index without a container runtime.

For CI/CD use cases it is often challenging to run a container runtime in a build job without adding additional privileges to the runner. So there is appetite to generate Indexes without any dependency on a container runtime, this has been shown by @kichik who has taken the logic out of the SOCI Index Builder into a standalone library https://github.com/CloudSnorkel/standalone-soci-indexer.

This feature request is to be able to build indexes without a container runtime either with the soci CLI or with a standalone binary.

Describe the solution you'd like

No response

Describe any alternative solutions/features you've considered

No response

Any additional context or information about the feature request

No response

@Kern--
Copy link
Contributor

Kern-- commented Jan 31, 2024

Related to #760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants