docker-machine support for use of volumes #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use docker-machine to run docker on a DigitalOcean instance, since my local machine has a tough time with some projects with a few containers.
It mostly works fine, and is meant to be a drop-in replacement for local docker on projects. But one thing docker-machine can't handle is local mounts (unnamed). (internally, docker expands the relative path locally like
./foo
to/Users/patcon/culturestake-provisioning/foo
, and so docker on the remote machine creates and mounts that empty dir on the server. Something about dockers architecture makes this not easily fixable, even though docker-machine is an official tool)Anyhow, if you felt ok merging this, it means people both with and without powerful workstations can contribute a bit easier. No pressure.
It adds a minimal Dockerfile for containers with those previous types of mounts, now with a COPY. docker-marchine sends the whole docker context to the server, so this works fine.
Further, might be able to use docker-gen as a mulitstage volume, where processed template is copied over, but wasn't clear enough on its operation to do it.