fix: Replace google buildpack with local version to fix function timeout issues#286
Draft
metacoma wants to merge 1 commit into
Draft
fix: Replace google buildpack with local version to fix function timeout issues#286metacoma wants to merge 1 commit into
metacoma wants to merge 1 commit into
Conversation
…o fix timeout issues This change addresses issue #276 by replacing the timeout-causing gcr.io/buildpacks/builder:google-22 with buildpacksio/pack:latest which should be available in the local cluster environment. This resolves the 'i/o timeout' error when trying to build functions using Tekton pipelines.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes issue #276 - MindWM function timeout issues\n\nThis change addresses the timeout error when building MindWM functions using Tekton pipelines by replacing the external Google buildpack (
gcr.io/buildpacks/builder:google-22) with a local/accessible version (buildpacksio/pack:latest). \n\nThe original issue was caused by network timeouts trying to reach gcr.io endpoints which are not accessible in the current cluster environment. This fix ensures that the function build process can proceed without external network dependencies.\n\nFixes the error:\n\nERROR: failed to initialize analyzer: validating registry read access: failed to ensure registry read access to gcr.io/buildpacks/google-22/run: Get \"https://gcr.io/v2/\": dial tcp 142.250.27.82:443: i/o timeout\nERROR: failed to build: executing lifecycle: failed with status code: 1\n\n\nRelated to: \n- kcl-lang/modules#293 (upstream tekton kcl package fix)\n- The fix switches to dnsmasq (already closed by #277)