-
Notifications
You must be signed in to change notification settings - Fork 377
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
Tweak and document disabling Docker build integration #5365
base: main
Are you sure you want to change the base?
Conversation
This pull request has merge conflicts that need to be resolved. |
094ccbd
to
be8b5e6
Compare
This pull request has merge conflicts that need to be resolved. |
be8b5e6
to
8ff47f6
Compare
README.md
Outdated
|
||
```shell | ||
make EMBEDDED_BINS_BUILDMODE=none | ||
``` | ||
|
||
The embedded binaries can be built on their own: | ||
As mentioned previously, Docker build integration is enabled by default. | ||
Building k0s without Docker using the system toolchain can be done as follows: |
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.
What do you mean by "system toolchain", maybe give an example what this means in this context
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.
PTAL. I tried to clarify this sentence.
The previous sentinel value of "false" may have given the impression that "true" is the correct value to enable Docker build integration. Also, "false" is actually an executable provided by coreutils. An empty string can never point to a potentially executable file, and won't give the impression that DOCKER is some sort of boolean variable. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
Don't default EMBEDDED_BINS_BUILDMODE to none when disabling Docker integration. This makes it clear that the binaries can't be built without it, at the moment. Inline the K0S_BUILD_IMAGE_FILE variable and replace it with the more generic GO_ENV_REQUISITES. Document the new variable in the README. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
8ff47f6
to
44c70df
Compare
Description
Don't default
EMBEDDED_BINS_BUILDMODE
to none when disabling Docker integration. This makes it clear that the binaries can't be built without it, at the moment. Inline theK0S_BUILD_IMAGE_FILE
variable and replace it with the more genericGO_ENV_REQUISITES
. Use the empty string to disable Docker integration: The previous sentinel value of "false" may have given the impression that "true" is the correct value to enable Docker build integration. Also, "false" is actually an executable provided by coreutils. An empty string can never point to a potentially executable file, and won't give the impression that DOCKER is some sort of boolean variable.Document the new build variables in the README.
Follow-up to:
Type of change
How Has This Been Tested?
Checklist: