Angular CLI installation fails on Ubuntu under Vagrant with killed

[manuelfink]

Having problems under osx with angular-cli I just thought trying it with vagrant and ubuntu.

Version

ubuntu-trusty-64
node v6.2.2
npm 3.10.2

Repro steps.

# ---- Vagrantfile ---
Vagrant.configure("2") do |config|
 #Use the Centos 6.5 image from the Vagrant cloud
 config.vm.box = "ubuntu/trusty64"
 config.vm.provider "virtualbox" do |v|
     v.memory = 1024
     v.cpus = 2
 end

 config.vm.provision "shell",
 path: "./vagrant/install-node.sh"

 config.vm.provision "shell",
 path: "./vagrant/install-angular2.sh"

 config.vm.provision "shell",
 path: "./vagrant/run-all.sh",
 run: "always"

 ###### Forward Ports
 config.vm.network "forwarded_port", host: 3000, guest: 3000, auto_correct: true    # Node
 config.vm.network "forwarded_port", guest: 6379, host: 6379, auto_correct: true    # Redis
 config.vm.network "forwarded_port", guest: 27019, host: 27019, auto_correct: true  # MongoDB
 config.vm.network "forwarded_port", host: 3306, guest: 3306, auto_correct: true    # MySQL
 config.vm.network "forwarded_port", host: 4200, guest: 4200, auto_correct: true    # angular server
 config.vm.network "forwarded_port", host: 49152, guest: 49152, auto_correct: true  # angular livereload server
 config.vm.network "forwarded_port", host: 35729, guest: 35729, auto_correct: true  # livereload server default port
end




# --- vagrant/install-node.sh ---
sudo -s
apt-get update
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
apt-get install -y nodejs
apt-get install -y build-essential
# apt-get install -y npm # needed to be seperatly installed with old version
npm install -g npm




# --- vagrant/install-angular2.sh ----
sudo -s
npm install -g angular-cli

log given by the failure

root@vagrant-ubuntu-trusty-64:~# npm install -g angular-cli
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
Killed        .....] - extract:angular-cli: sill doParallel extract 1380

no further error messages are available :(

[manuelfink]

Problem is caused by too less memory. Installation needs at least 1GB ram

[trickpattyFH20]

@manuelfink do you have any advice on how to work with angular-cli deployment on AWS or other cloud instances where memory is limited? I would like to adhere to the structure of src / dist and having the app built from src when deploying to prod.

Is there a simple way to manage this with angular-cli or will I have to go back to a custom build process with something like gulp?

[khaidinh]

@trickpattyFH20 You can add some swap on your constrained instances. I posted some links on #2630 if you still need it.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}