Eric Riebling

This looks like a good task for the CMU student team, given the existing task to survey all the tools for other parameters: processing time, limits on input recording duration,...

Another 'gotcha' with Docker: it requires root privileges to run. (maybe not always, but for certain things) - I remember the explanation being that because it's possible to run a...

Candidate Vagrantfile that can do docker or virtualbox provisioning: does not do anything about the problems incurred with Docker running up disk space in /var/lib/docker... [Dockerfile.txt](https://github.com/srvk/DiViMe/files/1972638/Dockerfile.txt) Bring up the Docker...

This may be a showstopper: Using Docker provider instead of Virtualbox, the shared "synced" host folder functionality is crippled. Guest OS does not necessarily have write permissions to host filesystem,...

In spite of these complaints; Vagrantfile updated to support Docker as a virtualization provider within Vagrant. Use (ubuntu) with: ``` chmod 777 . # make current directory world writable vagrant...

Tried it - current Vagrantfile, on a fresh Windows 10 computer with Vagrant and Docker installed, actually works! Other things tried: saving the running Docker Container as a Docker Image...

Marking closed, documentation here: https://github.com/srvk/DiViMe/wiki/InstallingWithDocker

Docker is really not a VM, and the more I read about the Docker philosophy, the less inclined I am to believe it's benefits will outweigh it's costs. https://www.linode.com/docs/applications/containers/when-and-why-to-use-docker/#when-not-to-use-docker Yes...

Here's an example of not understanding what is going on with Docker Images piling up, or how to remove them if new ones keep appearing: I don't want Docker images...

Current issue, a catch-22: We want things to run inside the Docker container as user 'vagrant' (it's baked into almost all our code) - but 'vagrant' doesn't have write permission...