-
Notifications
You must be signed in to change notification settings - Fork 16
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
Leverage skopeo for pipeline #19
Labels
enhancement
New feature or request
Comments
The tradeoff is in incorporating and trusting another party in the build process. |
To clarify, the third party in this case is Red Hat :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the CI/CD process builds the container image, then loads it into Docker and uses Docker to push it. I've had fairly good luck with using https:/containers/skopeo to push the Nix-built container image directly. It's a minor "optimization" (if you could call it that) but might be worth looking at.
Here's a rough example of where I'm using it for a personal repository: https://git.gmem.ca/arch/dref/src/branch/trunk/.gitea/workflows/test-build.yml#L36-L72
The text was updated successfully, but these errors were encountered: