4 ms·
Oh yeah, being able to specify dockerfiles is golden. We actually use Makefiles to copy docker files from different directories for building, then copying them
by carrja99 12y ago
Oh yeah, being able to specify dockerfiles is golden. We actually use Makefiles to copy docker files from different directories for building, then copying them back. What a hassle it has been.
- toomuchtodo 12y agoCouldn't you use symlinks that you create/unlink at build time?
- nbaksalyar 12y agoDocker explicitly forbids usage of symlinks. But there was a workaround: tar the entire directory and then build your container from the archive, like `tar cfh * | docker build -`. Hopefully that wouldn't be needed now.
- vacri 12y agoI ended up having to call container with nginx using a custom config file for each different environment. I've been waiting for this as well...
- echidna 12y agoYou could always use the "wrapper script pattern", e.g. http://blog.james-carr.org/2013/09/04/parameterized-docker-containers/ http://blog.james-carr.org/2013/09/04/parameterized-docker-c... or implement a ready-to-go solution like Tiller (https://github.com/markround/tiller https://github.com/markround/tiller) if you don't mind the overhead of ruby in your containers.