Fixing logrotate issue in Makefile/Dockerfile #3233
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Dependency DOCKER_BUILDKIT=1 in Makefile.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
make docker
RUN chmod -R u=rwX,go=rX /etc
in current Dockerfileiotex-core/Dockerfile
Line 32 in faf3c97
DOCKER_BUILDKIT=0 docker build -t jeremi/iotex-core:latest .
to compile successfully with no errors, but the build will fail if using BuildKitDOCKER_BUILDKIT=1 docker build -t jeremi/iotex-core:latest .
Since BuildKit is the recommended way to use Docker by Docker Support, as it is more optimized than regular docker build command without BuildKit, I propose to fix the issue by forcing the Makefile to use
and removing the breaking change
from the Dockerfile. This command is not necessary, since the error it throws when using
DOCKER_BUILDKIT=0
is not a fatal error, it is only an error in the display, like many others. The container complains aboutbut it is not a fatal error. The container will still build.
Thus my last commit was a breaking change. Sorry for the mistake, I did not test this previous fix with BuildKit, as I never used it before
I think the only way to avoid issues like these in the future is to build our own base image