Created
April 18, 2012 18:19
-
-
Save mccrory/2415596 to your computer and use it in GitHub Desktop.
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
| oot@ip-10-73-19-131:/tmp/bosh/release/template/instance# /var/vcap/bosh/bin/gem install chef --version 0.9.12 | |
| ERROR: Loading command: install (LoadError) | |
| no such file to load -- zlib | |
| ERROR: While executing gem ... (NameError) | |
| uninitialized constant Gem::Commands::InstallCommand |
Which of these packages are new from prepare_instance.sh? What patch do we make to that script?
Back in the remote terminal (you can copy and paste each chunk):
apt-get update
apt-get install git-core -y
apt-get install build-essential bison openssl libreadline6 libreadline6-dev curl git-core zlib1g zlib1g-dev libssl-dev libyaml-dev libsqlite3-0 libsqlite3-dev sqlite3 libxml2-dev libxslt-dev autoconf libc6-dev ncurses-dev
cd /tmp
git clone https://github.com/cloudfoundry/bosh.git
cd bosh/release/template/instance
./prepare_instance.sh
chmod 777 /var/vcap/deploy
exit
…On Apr 18, 2012, at 2:29 PM, Dr Nic Williams wrote:
Which of these packages are new from prepare_instance.sh? What patch do we make to that script?
---
Reply to this email directly or view it on GitHub:
https://gist.github.com/2415596
I don't understand why your scenario/example is different. For me, it all just works. prepare_instance.sh installs many of those packages itself (https://github.com/drnic/bosh/blob/master/release/template/instance/prepare_instance.sh#L18-24).
If we need all these packages, then they should go in the prepare_instance.sh script imo. I only install git-core manually so I can get the bosh repo.
I've linked this gist to an issue https://github.com/drnic/bosh-getting-started-on-aws/issues/8
You got me, I followed the directions and had to make that change for it to work...once I did all of it went smoothly..
Now about the directions to deploy the wordpress... ;-) Very confusing atm...
Seems like chicken and egg with the instances that need elastic IPs, but then arguably need DNS entries but the DNS can't exist until the instances do...
…On Apr 18, 2012, at 3:42 PM, Dr Nic Williams wrote:
I've linked this gist to an issue https://github.com/drnic/bosh-getting-started-on-aws/issues/8
---
Reply to this email directly or view it on GitHub:
https://gist.github.com/2415596
I haven't been back to the instructions since I got it working. I'll work on it now for you.
##
Dr Nic Williams
Engine Yard, VP Developer Evangelism
http://engineyard.com
http://drnicwilliams.com
http://about.me/drnic
cell +1 (415) 860-2185
…On Wednesday, April 18, 2012 at 3:50 PM, Dave McCrory wrote:
You got me, I followed the directions and had to make that change for it to work...once I did all of it went smoothly..
Now about the directions to deploy the wordpress... ;-) Very confusing atm...
Seems like chicken and egg with the instances that need elastic IPs, but then arguably need DNS entries but the DNS can't exist until the instances do...
On Apr 18, 2012, at 3:42 PM, Dr Nic Williams wrote:
> I've linked this gist to an issue https://github.com/drnic/bosh-getting-started-on-aws/issues/8
> ---
>
> Reply to this email directly or view it on GitHub:
> https://gist.github.com/2415596
---
Reply to this email directly or view it on GitHub:
https://gist.github.com/2415596
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
And the fix:
/usr/bin/apt-get install build-essential bison openssl libreadline6 libreadline6-dev curl git-core zlib1g zlib1g-dev libssl-dev libyaml-dev libsqlite3-0 libsqlite3-dev sqlite3 libxml2-dev libxslt-dev autoconf libc6-dev ncurses-dev