-
Notifications
You must be signed in to change notification settings - Fork 488
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
Add build image for windows boringcrypto executable. #6369
Conversation
Note I have built a fips windows version using my docker account mrdgrafana build image. |
I originally though about importing the core build image and only overwriting the go parts but then the build image needs to have another step and that seems painful. Basically would have to trigger a build on the normal build images, change the code for fips to use them, then trigger another build for the fips image. |
…d_image' into create_windows_boringcrypto_build_image
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…d_image' into create_windows_boringcrypto_build_image
* Add build image for windows boringcrypto executable. * Update Dockerfile * Update build_image.jsonnet * Use ARG instead of duplicate image * force the usage of arg
PR Description
This lays the groundwork for building windows agent flow using boring crypto. The important bit for this is
FROM mcr.microsoft.com/oss/go/microsoft/golang:1.22-bullseye as golang
which tells it to use the fips compatible windows golang runtime.Not adding a changelog until the second part of the pr to use the built image.
At some point may switch the linux version to using this so its cleaner on what builds what.