chore: Update Dockerfile.local to fix build process when target folder is already generated in the code context
#185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t` directory from native cargo build process exists in the finalinzer code folder
iStrike7
approved these changes
Jul 15, 2024
tenequm
deleted the
fix/local-finalizer-build-compatibility-with-regular-non-containerized-cargo-build
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates the Dockerfile.local to ensure that the build process does not break when the
targetdirectory from the native cargo build process exists in the finalizer code folder. The changes include modifying the base image, adding new build stages, and removing the local build directory to avoid interference with the cached dependencies. This update improves the reliability and stability of the build process.