-
Notifications
You must be signed in to change notification settings - Fork 82
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
docs: redirect users to use make targets on builds #1990
docs: redirect users to use make targets on builds #1990
Conversation
ce7fbc9
to
995f637
Compare
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
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. Thanks!
995f637
to
0b7eded
Compare
@wainersm thanks for your comment, I fixed the main one with a force-push. let me know if you are ok with it now. |
@wainersm @beraldoleal - FYI I'm think of doing the same change as this for the podvm_builder as well (to redirect people to use the |
Current dockerfiles are not ready to build directly from the folder. Builder is broken as also depends on .git and .hack folders. Make targets are working, so lets redirect our readers to use those targets. We can improve the targets as needed and this will be transparant for the readers. Signed-off-by: Beraldo Leal <[email protected]>
0b7eded
to
b8df264
Compare
Similar to confidential-containers#1990, update the podvm_builder documentation to use the `make` command, rather than the docker file directly to hide the complexity and allow the versions to be picked up automatically Signed-off-by: stevenhorsman <[email protected]>
Similar to confidential-containers#1990, update the podvm_builder documentation to use the `make` command, rather than the docker file directly to hide the complexity and allow the versions to be picked up automatically Signed-off-by: stevenhorsman <[email protected]>
@stevenhorsman @beraldoleal can we merge this ? |
Similar to confidential-containers#1990, update the podvm_builder documentation to use the `make` command, rather than the docker file directly to hide the complexity and allow the versions to be picked up automatically Signed-off-by: stevenhorsman <[email protected]>
Yeah, I happy with that. |
Similar to confidential-containers#1990, update the podvm_builder documentation to use the `make` command, rather than the docker file directly to hide the complexity and allow the versions to be picked up automatically Signed-off-by: stevenhorsman <[email protected]>
Similar to #1990, update the podvm_builder documentation to use the `make` command, rather than the docker file directly to hide the complexity and allow the versions to be picked up automatically Signed-off-by: stevenhorsman <[email protected]>
Current dockerfiles are not ready to build directly from the folder. Builder is broken as also depends on .git and .hack folders. Make targets are working, so lets redirect our readers to use those targets.
We can improve the targets as needed and this will be transparant for the readers.