I've been working on getting a dev environment set up with docker over the weekend, and I finally have something I'm happy with.
I don't have a nice blog post to show you, but the basic idea is:
- Use the CoreOS Vagrantfile (+ extra files like user_data and any service unit files)
- Share your local directory with the vagrant box with config.vm.synced_folder (just uncomment a line in the Vagrantfile)
- set the DOCKER_HOST and FLEETCTL_TUNNEL env variables so that the local tools work transparently with the vagrant box.
- Then you have the option of running a docker image with -v and sharing the vagrant directory with the docker container, or
- You can dive into CoreOS stuff and write a unit file for your service, and that will share the directory with -v
Now local files sync into the docker container, and if the server is configured to reload on file changes you're good to go.
I don't have a nice blog post to show you, but the basic idea is:
- Use the CoreOS Vagrantfile (+ extra files like user_data and any service unit files)
- Share your local directory with the vagrant box with config.vm.synced_folder (just uncomment a line in the Vagrantfile)
- set the DOCKER_HOST and FLEETCTL_TUNNEL env variables so that the local tools work transparently with the vagrant box.
- Then you have the option of running a docker image with -v and sharing the vagrant directory with the docker container, or
- You can dive into CoreOS stuff and write a unit file for your service, and that will share the directory with -v
Now local files sync into the docker container, and if the server is configured to reload on file changes you're good to go.