gistfile1.txt

λ vagrant ssh
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.


Last login: Mon Oct 24 16:51:52 2016 from 10.0.2.2
ubuntu@katuma:~$ mkdir dummy-node
ubuntu@katuma:~$ cd dummy-node/
ubuntu@katuma:~/dummy-node$ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.

See `npm help json` for definitive documentation on these fields
and exactly what they do.

Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.

Press ^C at any time to quit.
name: (dummy-node) 
version: (1.0.0) 
description: 
entry point: (index.js) 
test command: 
git repository: 
keywords: 
author: 
license: (ISC) 
About to write to /home/ubuntu/dummy-node/package.json:

{
  "name": "dummy-node",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}


Is this ok? (yes) 
ubuntu@katuma:~/dummy-node$ npm i
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
ubuntu@katuma:~/dummy-node$ npm i express --save
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm ERR! tar.unpack error reading /home/ubuntu/.npm/destroy/1.0.4/package.tgz
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "i" "express" "--save"
npm ERR! node v4.6.1
npm ERR! npm  v2.15.9
npm ERR! code EIO
npm ERR! errno -5
npm ERR! syscall read

npm ERR! EIO: i/o error, read
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! error rolling back Error: EROFS: read-only file system, rmdir '/home/ubuntu/dummy-node/node_modules/express/node_modules/type-is'
npm ERR! error rolling back     at Error (native)
npm ERR! error rolling back  { [Error: EROFS: read-only file system, rmdir '/home/ubuntu/dummy-node/node_modules/express/node_modules/type-is']
npm ERR! error rolling back   errno: -30,
npm ERR! error rolling back   code: 'EROFS',
npm ERR! error rolling back   syscall: 'rmdir',
npm ERR! error rolling back   path: '/home/ubuntu/dummy-node/node_modules/express/node_modules/type-is' }
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "i" "express" "--save"
npm ERR! node v4.6.1
npm ERR! npm  v2.15.9
npm ERR! path npm-debug.log.1276125115
npm ERR! code EROFS
npm ERR! errno -30
npm ERR! syscall open

npm ERR! rofs EROFS: read-only file system, open 'npm-debug.log.1276125115'
npm ERR! rofs This is most likely not a problem with npm itself
npm ERR! rofs and is related to the file system being read-only.
npm ERR! rofs 
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/dummy-node/npm-debug.log