You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
Preparing to start container-info-test... OK
-----> Downloaded app package (4.0K)
fatal: Unable to look up github.com (port 9418) (Temporary failure in name resolution)
Initialized empty Git repository in /tmp/buildpacks/container-info-buildpack.git/.git/
/var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:115:in `clone_buildpack': Failed to git clone buildpack (RuntimeError)
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:91:in `build_pack'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:72:in `block in compile_with_timeout'
from /usr/lib/ruby/1.9.1/timeout.rb:68:in `timeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:71:in `compile_with_timeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:53:in `block in stage_application'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:49:in `chdir'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:49:in `stage_application'
from /var/vcap/packages/dea_next/buildpacks/bin/run:10:in `<main>'
Checking status of app 'container-info-test'...Application failed to stage
The text was updated successfully, but these errors were encountered:
New BOSH user here, I ran into these problems with Virtualbox repeatedly and resolved them when I added these two lines to the Vagrant file's virtualbox provider config:
config.vm.provider :virtualbox do |v, override|
# ...
v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
v.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
end
Which forwards DNS requests to the outer host and doesn't muck with the guest when DNS servers change due to switching DHCP networks. Also works well with offline modes using Dnsmasq.
Just tried @drnic's test case above with a fresh bosh-lite and it worked fine.
When I deploy an app into CF within bosh-lite, it must have all its assets (and not use a public buildpack) as it cannot access the public internet:
Following https://github.com/cloudfoundry-community/container-info-buildpack/blob/master/README.md
The text was updated successfully, but these errors were encountered: