-
Notifications
You must be signed in to change notification settings - Fork 48
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
apt-buildpack https support (apt-transport-https) #20
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/165684025 The labels on this github issue will be updated when the story is started. |
Thanks @lrstanley, Not sure if this is possible. To me it seems we would have to install the https module from a local deb package in order to make this work. But I'm not sure. @sclevine ideas? |
Duplicate of: #9. Please use cflinuxfs3 as cflinuxfs2 is no longer supported. Thanks. |
Thanks, didn't notice that existing issue. |
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
? cf-cli: v6.43.0 and cf version: 2.2.9-build.5 and tested with 2.3.8-build.6.What version of the buildpack you are using? v0.1.6
If you were attempting to accomplish a task, what was it you were attempting to do? use an Artifactory based Ubuntu repository, as we are unable to access ubuntu repos directly due to corporate firewall reasons.
What did you expect to happen? It to fetch packages from Artifactory as if it were fetching from Ubuntu directly.
What was the actual behavior? Our Artifactory cluster is https only, which requires the https module for apt. I believe it is failing out because the buildpack doesn't have the https module.
Please confirm where necessary:
Deploy logs:
Repo:
apt.yml
:Sidenote: I also noticed that if I didn't specify Artifactory, because Ubuntu is blocked, it just succeeded, but didn't show it was installed when I logged into the container. I think this may be similar to #19
The text was updated successfully, but these errors were encountered: