Vagrant install fail


“Vagrant up” has failed on my company computer.
Is there any way to install properly?
What do I need to ask corp administrator?


Microsoft Windows [Version 10.0.17763.973]
© 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \

C:>cd users\bkim\m103

C:\Users\bkim\m103>cd m103_vagrant_env
The system cannot find the path specified.

C:\Users\bkim\m103>cd m103_vagrant_env
The system cannot find the path specified.

C:\Users\bkim\m103>cd m103_vagrant_env
The system cannot find the path specified.

Volume in drive C has no label.
Volume Serial Number is B68F-2595

Directory of C:\Users\bkim\m103

02/08/2020 09:52 AM .
02/08/2020 09:52 AM …
02/08/2020 09:52 AM m103-vagrant-env
0 File(s) 0 bytes
3 Dir(s) 143,196,131,328 bytes free

C:\Users\bkim\m103>cd m103-vagrant-env

C:\Users\bkim\m103\m103-vagrant-env>vagrant up
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Box ‘ubuntu/trusty64’ could not be found. Attempting to find and install…
mongod-m103: Box Provider: virtualbox
mongod-m103: Box Version: >= 0
==> mongod-m103: Loading metadata for box ‘ubuntu/trusty64’
mongod-m103: URL:
==> mongod-m103: Adding box ‘ubuntu/trusty64’ (v20190514.0.0) for provider: virtualbox
mongod-m103: Downloading:
mongod-m103: Download redirected to host:
==> mongod-m103: Successfully added box ‘ubuntu/trusty64’ (v20190514.0.0) for ‘virtualbox’!
==> mongod-m103: Importing base box ‘ubuntu/trusty64’…
==> mongod-m103: Matching MAC address for NAT networking…
==> mongod-m103: Setting the name of the VM: mongod-m103
==> mongod-m103: Clearing any previously set forwarded ports…
Vagrant is currently configured to create VirtualBox synced folders with
the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

This option can be disabled globally with an environment variable:


or on a per folder basis within the Vagrantfile:

config.vm.synced_folder ‘/host/path’, ‘/guest/path’, SharedFoldersEnableSymlinksCreate: false
==> mongod-m103: Clearing any previously set network interfaces…
==> mongod-m103: Preparing network interfaces based on configuration…
mongod-m103: Adapter 1: nat
mongod-m103: Adapter 2: hostonly
==> mongod-m103: Forwarding ports…
mongod-m103: 22 (guest) => 2222 (host) (adapter 1)
==> mongod-m103: Running ‘pre-boot’ VM customizations…
==> mongod-m103: Booting VM…
==> mongod-m103: Waiting for machine to boot. This may take a few minutes…
mongod-m103: SSH address:
mongod-m103: SSH username: vagrant
mongod-m103: SSH auth method: private key
mongod-m103: Vagrant insecure key detected. Vagrant will automatically replace
mongod-m103: this with a newly generated keypair for better security.
mongod-m103: Inserting generated public key within guest…
mongod-m103: Removing insecure key from the guest if it’s present…
mongod-m103: Key inserted! Disconnecting and reconnecting using new SSH key…
==> mongod-m103: Machine booted and ready!
==> mongod-m103: Checking for guest additions in VM…
mongod-m103: The guest additions on this VM do not match the installed version of
mongod-m103: VirtualBox! In most cases this is fine, but in rare cases it can
mongod-m103: prevent things such as shared folders from working properly. If you see
mongod-m103: shared folder errors, please make sure the guest additions within the
mongod-m103: virtual machine match the version of VirtualBox you have installed on
mongod-m103: your host and reload your VM.
mongod-m103: Guest Additions Version: 4.3.40
mongod-m103: VirtualBox Version: 6.0
==> mongod-m103: Setting hostname…
==> mongod-m103: Configuring and enabling network interfaces…
==> mongod-m103: Mounting shared folders…
mongod-m103: /shared => C:/Users/bkim/m103/m103-vagrant-env/shared
mongod-m103: /vagrant => C:/Users/bkim/m103/m103-vagrant-env
mongod-m103: /dataset => C:/Users/bkim/m103/m103-vagrant-env/dataset
==> mongod-m103: Running provisioner: shell…
mongod-m103: Running: C:/Users/bkim/AppData/Local/Temp/vagrant-shell20200208-2624-rbw2hr
mongod-m103: + config
mongod-m103: + sudo su
mongod-m103: + echo -e never
mongod-m103: + echo -e never
mongod-m103: + sudo tee /etc/init/mongod.override
mongod-m103: + echo manual
mongod-m103: manual
mongod-m103: + ip_config
mongod-m103: ++ ifconfig
mongod-m103: ++ grep ‘inet addr:’
mongod-m103: ++ tail -1
mongod-m103: ++ awk ‘{ print $1}’
mongod-m103: ++ grep -v
mongod-m103: ++ cut -d: -f2
mongod-m103: + export CLIENT_IP_ADDR=
mongod-m103: + CLIENT_IP_ADDR=
mongod-m103: ++ tr ‘[:upper:]’ ‘[:lower:]’
mongod-m103: ++ cut -d. -f 1
mongod-m103: ++ hostname
mongod-m103: + export CLIENT_NAME=m103
mongod-m103: + CLIENT_NAME=m103
mongod-m103: + echo ‘Configuring /etc/hosts …’
mongod-m103: Configuring /etc/hosts …
mongod-m103: + echo ' localhost localhost.localdomain localhost4 localhost4.localdomain4 ’
mongod-m103: + echo ‘::1 localhost localhost.localdomain localhost6 localhost6.localdomain6’
mongod-m103: + echo ‘fe00::0 ip6-localnet’
mongod-m103: + echo ‘ff00::0 ip6-mcastprefix’
mongod-m103: + echo ‘ff02::1 ip6-allnodes’
mongod-m103: + echo ‘ff02::2 ip6-allrouters’
mongod-m103: + echo ‘ff02::3 ip6-allhosts’
mongod-m103: + echo ‘ m103’
mongod-m103: Install MongoDB Enterprise Repository
mongod-m103: + update_repo
mongod-m103: + echo ‘Install MongoDB Enterprise Repository’
mongod-m103: + echo ‘deb [ arch=amd64 ] trusty/mongodb-enterprise/3.6 multiverse’
mongod-m103: + sudo tee /etc/apt/sources.list.d/mongodb-enterprise.list
mongod-m103: deb [ arch=amd64 ] trusty/mongodb-enterprise/3.6 multiverse
mongod-m103: + sudo apt-key adv --keyserver --recv 0C49F3730359A14518585931BC711F9BA15703C6
mongod-m103: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.373caLZCPF --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/ubuntu-advantage-esm-infra-trusty.gpg --keyserver --recv 0C49F3730359A14518585931BC711F9BA15703C6
mongod-m103: gpg:
mongod-m103: requesting key A15703C6 from hkp server
mongod-m103: gpg:
mongod-m103: key A15703C6: public key “MongoDB 3.4 Release Signing Key” imported
mongod-m103: gpg:
mongod-m103: Total number processed: 1
mongod-m103: gpg:
mongod-m103: imported: 1
mongod-m103: (RSA: 1)
mongod-m103: + echo ‘Update Repositories’
mongod-m103: Update Repositories
mongod-m103: + sudo apt-get update -y
mongod-m103: Ign trusty InRelease
mongod-m103: Hit trusty-security InRelease
mongod-m103: Get:1 trusty-updates InRelease [65.9 kB]
mongod-m103: Get:2 trusty-security/main Sources [172 kB]
mongod-m103: Get:3 trusty-infra-security InRelease
mongod-m103: Get:4 trusty-infra-updates InRelease
mongod-m103: Get:5 trusty-infra-security/main amd64 Packages
mongod-m103: Hit trusty-backports InRelease
mongod-m103: Get:6 trusty-infra-security/main Translation-en_US
mongod-m103: Hit trusty Release.gpg
mongod-m103: Get:7 trusty-security/universe Sources [102 kB]
mongod-m103: Get:8 trusty-updates/main Sources [431 kB]
mongod-m103: Get:9 trusty-infra-updates/main Translation-en_US
mongod-m103: Hit trusty-security/main amd64 Packages
mongod-m103: Hit trusty-security/universe amd64 Packages
mongod-m103: Hit trusty-security/main Translation-en
mongod-m103: Get:10 trusty-updates/restricted Sources [6,313 B]
mongod-m103: Hit trusty-security/universe Translation-en
mongod-m103: Get:11 trusty-updates/universe Sources [231 kB]
mongod-m103: Get:12 trusty-updates/multiverse Sources [7,535 B]
mongod-m103: Ign trusty-infra-security/main Translation-en_US
mongod-m103: Ign trusty-infra-security/main Translation-en
mongod-m103: Get:13 trusty-updates/main amd64 Packages [1,177 kB]
mongod-m103: Ign trusty-infra-updates/main Translation-en_US
mongod-m103: Ign trusty-infra-updates/main Translation-en
mongod-m103: Get:14 trusty-updates/restricted amd64 Packages [17.2 kB]
mongod-m103: Get:15 trusty-updates/universe amd64 Packages [525 kB]
mongod-m103: Get:16 trusty-updates/multiverse amd64 Packages [14.6 kB]
mongod-m103: Get:17 trusty-updates/main Translation-en [582 kB]
mongod-m103: Get:18 trusty-updates/multiverse Translation-en [7,616 B]
mongod-m103: Get:19 trusty-updates/restricted Translation-en [4,028 B]
mongod-m103: Get:20 trusty-updates/universe Translation-en [281 kB]
mongod-m103: Get:21 trusty-backports/main Sources [9,709 B]
mongod-m103: Get:22 trusty-backports/restricted Sources [28 B]
mongod-m103: Get:23 trusty-backports/universe Sources [35.4 kB]
mongod-m103: Get:24 trusty-backports/multiverse Sources [1,896 B]
mongod-m103: Hit trusty-backports/main amd64 Packages
mongod-m103: Hit trusty-backports/restricted amd64 Packages
mongod-m103: Hit trusty-backports/universe amd64 Packages
mongod-m103: Hit trusty-backports/multiverse amd64 Packages
mongod-m103: Hit trusty-backports/main Translation-en
mongod-m103: Hit trusty-backports/multiverse Translation-en
mongod-m103: Hit trusty-backports/restricted Translation-en
mongod-m103: Hit trusty-backports/universe Translation-en
mongod-m103: Hit trusty Release
mongod-m103: Get:25 trusty/main Sources [1,064 kB]
mongod-m103: Get:26 trusty/restricted Sources [5,433 B]
mongod-m103: Get:27 trusty/universe Sources [6,399 kB]
mongod-m103: Get:28 trusty/multiverse Sources [174 kB]
mongod-m103: Hit trusty/main amd64 Packages
mongod-m103: Hit trusty/restricted amd64 Packages
mongod-m103: Hit trusty/universe amd64 Packages
mongod-m103: Hit trusty/multiverse amd64 Packages
mongod-m103: Hit trusty/main Translation-en
mongod-m103: Hit trusty/multiverse Translation-en
mongod-m103: Hit trusty/restricted Translation-en
mongod-m103: Hit trusty/universe Translation-en
mongod-m103: Ign trusty/main Translation-en_US
mongod-m103: Ign trusty/multiverse Translation-en_US
mongod-m103: Ign trusty/restricted Translation-en_US
mongod-m103: Ign trusty/universe Translation-en_US
mongod-m103: Err trusty/mongodb-enterprise/3.6 InRelease
mongod-m103: Err trusty/mongodb-enterprise/3.6 Release.gpg
mongod-m103: Could not resolve ‘
mongod-m103: Fetched 11.6 MB in 4min 14s (45.6 kB/s)
mongod-m103: Reading package lists…
mongod-m103: W
mongod-m103: :
mongod-m103: Failed to fetch
mongod-m103: W
mongod-m103: :
mongod-m103: Failed to fetch Could not resolve ‘
mongod-m103: W
mongod-m103: :
mongod-m103: Some index files failed to download. They have been ignored, or old ones used instead.
mongod-m103: + echo ‘Installing MongoDB Enterprise Dependencies’
mongod-m103: Installing MongoDB Enterprise Dependencies
mongod-m103: + sudo apt-get install -y libgssapi-krb5-2 libsasl2-2 libssl1.0.0 libstdc++6 snmp
mongod-m103: Reading package lists…
mongod-m103: Building dependency tree…
mongod-m103: Reading state information…
mongod-m103: libsasl2-2 is already the newest version.
mongod-m103: libgssapi-krb5-2 is already the newest version.
mongod-m103: libssl1.0.0 is already the newest version.
mongod-m103: libstdc++6 is already the newest version.
mongod-m103: Suggested packages:
mongod-m103: lm-sensors snmp-mibs-downloader
mongod-m103: The following NEW packages will be installed:
mongod-m103: libperl5.18 libsensors4 libsnmp-base libsnmp30 snmp
mongod-m103: 0 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
mongod-m103: Need to get 1,167 kB of archives.
mongod-m103: After this operation, 4,676 kB of additional disk space will be used.
mongod-m103: Get:1 trusty/main libsensors4 amd64 1:3.3.4-2ubuntu1 [27.2 kB]
mongod-m103: Get:2 trusty-updates/main libperl5.18 amd64 5.18.2-2ubuntu1.7 [1,330 B]
mongod-m103: Get:3 trusty-updates/main libsnmp-base all 5.7.2~dfsg-8.1ubuntu3.3 [203 kB]
mongod-m103: Get:4 trusty-updates/main libsnmp30 amd64 5.7.2~dfsg-8.1ubuntu3.3 [789 kB]
mongod-m103: Get:5 trusty-updates/main snmp amd64 5.7.2~dfsg-8.1ubuntu3.3 [146 kB]
mongod-m103: dpkg-preconfigure: unable to re-open stdin: No such file or directory
mongod-m103: Fetched 1,167 kB in 3s (382 kB/s)
mongod-m103: Selecting previously unselected package libsensors4:amd64.
mongod-m103: (Reading database … 63238 files and directories currently installed.)
mongod-m103: Preparing to unpack …/libsensors4_1%3a3.3.4-2ubuntu1_amd64.deb …
mongod-m103: Unpacking libsensors4:amd64 (1:3.3.4-2ubuntu1) …
mongod-m103: Selecting previously unselected package libperl5.18.
mongod-m103: Preparing to unpack …/libperl5.18_5.18.2-2ubuntu1.7_amd64.deb …
mongod-m103: Unpacking libperl5.18 (5.18.2-2ubuntu1.7) …
mongod-m103: Selecting previously unselected package libsnmp-base.
mongod-m103: Preparing to unpack …/libsnmp-base_5.7.2~dfsg-8.1ubuntu3.3_all.deb …
mongod-m103: Unpacking libsnmp-base (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Selecting previously unselected package libsnmp30:amd64.
mongod-m103: Preparing to unpack …/libsnmp30_5.7.2~dfsg-8.1ubuntu3.3_amd64.deb …
mongod-m103: Unpacking libsnmp30:amd64 (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Selecting previously unselected package snmp.
mongod-m103: Preparing to unpack …/snmp_5.7.2~dfsg-8.1ubuntu3.3_amd64.deb …
mongod-m103: Unpacking snmp (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Processing triggers for man-db ( …
mongod-m103: Setting up libsensors4:amd64 (1:3.3.4-2ubuntu1) …
mongod-m103: Setting up libperl5.18 (5.18.2-2ubuntu1.7) …
mongod-m103: Setting up libsnmp-base (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Setting up libsnmp30:amd64 (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Setting up snmp (5.7.2~dfsg-8.1ubuntu3.3) …
mongod-m103: Processing triggers for libc-bin (2.19-0ubuntu6.15) …
mongod-m103: + install_mongod
mongod-m103: + echo ‘Install MongoDB Enterprise’
mongod-m103: Install MongoDB Enterprise
mongod-m103: + sudo apt-get install --force-yes -y mongodb-enterprise
mongod-m103: Reading package lists…
mongod-m103: Building dependency tree…
mongod-m103: Reading state information…
mongod-m103: E
mongod-m103: :
mongod-m103: Unable to locate package mongodb-enterprise
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.


This error could be caused by a couple of things:

  1. VPN
  2. Corporate Network / Proxy
  3. Firewall
  4. Slow WiFi
  5. Anti-virus

It appears that you’re on a Corporate Network using a Corporate machine. Where possible, try disabling some of the above and run it on a Wired connection at home.
With regards proxy, you can setup vagrant to use a proxy but the firewall may also be a blocker, so ask your Sys Admin to temporarily sort out 2, 3, 5 and proceed to:

  1. vagrant destroy -f
  2. vagrant up

Thank you very much for answering.
I will ask copr admin about that.
I have private desktop pc and I’ve installed everything without any issue.
I’ve exported the image on VitualBox and imported my corp desktop.
The imported ubunt is working perfectly, but vagrant command doesn’t work with imported image.
Is there any way for vagrant to work together with the imported ubunt?

Thanks you.

This is more of DevOps/Sys Admin question which I’m not, but you should be able to package it and replay it elsewhere.

Also, vagrant stores its machine specific config and box files in two locations: your user’s home dir and the other in the dir is located where you vagrant and provision files are. You can try and copy those, however, I would imagine that there will be machine specific configs that will cause it to break so this process would most likely not work.

Suggest you sort it out with your Corp Admin.