Skip to content
This repository was archived by the owner on Jan 30, 2026. It is now read-only.
This repository was archived by the owner on Jan 30, 2026. It is now read-only.

DCS not coming up after successful install and use (days earlier) #3

@rduerr

Description

@rduerr

My local copy of the DCS will no longer start up. I do have data in it, so would like to get it going so that I can use it for my API-X use case. I suspect that the API-X proof-of-concept code installed locally as well, did this since this instance was working until that code was loaded. Suggestions?

Ruths-iMac:dcs-images ruthduerr$ vagrant up
Bringing machine 'dcs-container' up with 'docker' provider...
==> dcs-container: Docker host is required. One will be created if necessary...
dcs-container: Vagrant will now create or start a local VM to act as the Docker
dcs-container: host. You'll see the output of the vagrant up for this VM below.
dcs-container:
dockerhost: Checking if box 'ubuntu/trusty64' is up to date...
dockerhost: A newer version of the box 'ubuntu/trusty64' is available! You currently
dockerhost: have version '20160224.0.0'. The latest is version '20160602.0.0'. Run
dockerhost: vagrant box update to update.
dockerhost: Clearing any previously set forwarded ports...
dockerhost: Clearing any previously set network interfaces...
dockerhost: Preparing network interfaces based on configuration...
dockerhost: Adapter 1: nat
dockerhost: Adapter 2: hostonly
dockerhost: Forwarding ports...
dockerhost: 8080 (guest) => 8085 (host) (adapter 1)
dockerhost: 8181 (guest) => 8185 (host) (adapter 1)
dockerhost: 22 (guest) => 2222 (host) (adapter 1)
dockerhost: Running 'pre-boot' VM customizations...
dockerhost: Booting VM...
dockerhost: Waiting for machine to boot. This may take a few minutes...
dockerhost: SSH address: 127.0.0.1:2222
dockerhost: SSH username: vagrant
dockerhost: SSH auth method: private key
dockerhost: Warning: Remote connection disconnect. Retrying...
dockerhost: Machine booted and ready!
dockerhost: Checking for guest additions in VM...
dockerhost: The guest additions on this VM do not match the installed version of
dockerhost: VirtualBox! In most cases this is fine, but in rare cases it can
dockerhost: prevent things such as shared folders from working properly. If you see
dockerhost: shared folder errors, please make sure the guest additions within the
dockerhost: virtual machine match the version of VirtualBox you have installed on
dockerhost: your host and reload your VM.
dockerhost:
dockerhost: Guest Additions Version: 4.3.36
dockerhost: VirtualBox Version: 5.0
dockerhost: Configuring and enabling network interfaces...
dockerhost: Exporting NFS shared folders...
dockerhost: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
dockerhost: Mounting NFS shared folders...
dockerhost: Mounting shared folders...
dockerhost: /vagrant => /Users/ruthduerr/dcs/dcs-images
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t vboxsf -o uid=id -u vagrant,gid=getent group vagrant | cut -d: -f3 vagrant /vagrant
mount -t vboxsf -o uid=id -u vagrant,gid=id -g vagrant vagrant /vagrant

The error output from the last command was:

stdin: is not a tty
/sbin/mount.vboxsf: mounting failed with the error: No such device

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions