Setting up Shell Script for Vagrant Setup

Question

Trying to write a shell script to setup my server environment on Ubuntu through Vagrant and am running into a problem where the script ends unexpectedly. I added the path to the shell script in Vagrant's provision config option.

Vagrant:

# Specify our provision script
config.vm.provision "shell", path: "scripts/bootstrap.sh"

My script:

#!/bin/bash

# Install dependencies for Ruby
sudo apt-get update
sudo apt-get install -y git-core curl zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev software-properties-common

# Setting up rbenv
echo 'Setting up rbenv'
git clone git://github.com/sstephenson/rbenv.git .rbenv
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(rbenv init -)"' >> ~/.bashrc
exec $SHELL

After running, I expect the repository to be cloned into the .rbenv folder and to have rbenv added to $PATH in ~/.bashrc along with the rbenv init function evaluated and put into ~/.bashrc. However, when the script is executed on Vagrant's provision step I end up with the script just cloning the git repository and then terminating without executing anything else in my script.

Output:

==> default: Processing triggers for libc-bin (2.19-0ubuntu6) ...
==> default: Setting up rbenv
==> default: Cloning into '.rbenv'...

And then the script terminates and ~/.bashrc is left unchanged. I was wondering how I can change my shell script so that it will perform the action I want (which is adding rbenv to ~/.bashrc). Any ideas?

Is the script executed in the context of the current user? Could it be that ~ points elsewhere when the script runs? For debugging, add the following to your script and capture its stderr output as well: PS4='>$LINENO: '; set -xv — mklement0
– mklement0, Commented May 24, 2014 at 5:26

Community · Accepted Answer · 2017-05-23 11:52:53Z

8

As mklement0 said, the script does not run as the vagrant user: it runs as root.

If you want to run the script as the vagrant user you need privileged: false.

config.vm.provision :shell, privileged: false, path: "scripts/bootstrap.sh"

As mklement0 said: use set -xv to debug your provisioning scripts.

If you want to run as another user, don't forget that su user won't work: How do I use su to execute the rest of the bash script as that user?

edited May 23, 2017 at 11:52

CommunityBot

11 silver badge

answered May 24, 2014 at 6:17

Ciro Santilli OurBigBook.com

392k120 gold badges1.3k silver badges1.1k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Adam Michna · Accepted Answer · 2015-02-18 09:06:02Z

2

If you want execute some script like vagrant user, try this.

 su vagrant -l -c "echo Hello world"

answered Feb 18, 2015 at 9:06

Adam Michna

1691 silver badge7 bronze badges

Collectives™ on Stack Overflow

Setting up Shell Script for Vagrant Setup

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related