Skip to content
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

pack build failed with corporate network #644

Open
tppalani opened this issue Oct 27, 2023 · 0 comments
Open

pack build failed with corporate network #644

tppalani opened this issue Oct 27, 2023 · 0 comments

Comments

@tppalani
Copy link

Expected Behavior

pack build command failed when i connected my system within VPN network.

  1. Sample repo has been cloned from https://github.com/paketo-buildpacks/samples
  2. I'm trying build npm app under the location https://github.com/paketo-buildpacks/samples/tree/main/nodejs/npm
  3. Under this path https://github.com/paketo-buildpacks/samples/tree/main/nodejs/npm in my local i have create folder name ca-certificates/binding/root.pem then i kept root.pem file
  4. when i'm running build command
pack build --volume "C:/Users/workspace/caas-devops-tekton-pipelines/buildpack-cli/samples/nodejs/npm/ca-certificates/binding:/bindings/ca-certificates" npm-app:1.0 --docker-host=unix:///run/podman/podman.sock --builder paketobuildpacks/builder:base
  1. Build getting failed with TLS certificate issue.

Current Behavior

Executing build process
Installing Node Engine 18.16.1
failed to fetch dependency: failed to make request: Get "https://artifacts.paketo.io/node/node_v18.16.1_linux_x64_bionic_60e34618.tgz": tls: failed to verify certificate: x509: certificate signed by unknown authority

Possible Solution

Steps to Reproduce

Motivations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant