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

Build OCI artifacts and save to the registry #5995

Open
1 task done
nabokihms opened this issue Mar 8, 2024 · 0 comments
Open
1 task done

Build OCI artifacts and save to the registry #5995

nabokihms opened this issue Mar 8, 2024 · 0 comments

Comments

@nabokihms
Copy link

Before proceeding

  • I didn't find a similar issue

Problem

Currently, there is no functionality in werf to save images as OCI artifacts during the build stage.
Some artifacts are required to be saved in the container registry for further distribution, e.g., to build and distribute binaries.

Solution (if you have one)

Introduce the capability to save images as OCI artifacts during the build process in werf. This feature would allow users to produce OCI-compliant artifacts directly from their builds, enhancing interoperability and compatibility with other container tools and platforms.

The example of the possible werf.yaml to show the idea.

image: my-app
artifact: true
git:
- add: /
  to: /src
shell:
  install:
  - go build /src/main.go -o /my-app
---
image: my-app-binary
oci: true
fromArtifact: my-app
filePath: /my-app
mediatype: application/vnd.my-company.golang.binary.content.v1

As a result, the /my-app binary from the my-app artifact will be uploaded to the container registry.

Additional information

By enabling the option to save images as OCI artifacts, werf users can benefit from improved portability and standardized image distribution. OCI artifacts offer advantages such as reduced complexity, increased security, and better support for multi-platform environments. This enhancement aligns with industry best practices and enhances the overall usability and versatility of the werf tool.

For more information about OCI (Open Container Initiative) standards, please refer to the official OCI website: Open Container Initiative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants