Create Dockerfile #255
Create Dockerfile #255
Conversation
It's a file that will allow lib to run outside of its happy native debian environment, for example, on arch, or in fact... anywhere. That should actually do it, that single line. I can make it more complicated if need be, but I think that will work..... wait wait wait, have to do something about the path relativity, so..... I had it clone the repository anyway instead of just using the files that Docker will automatically copy over. May want to put this in igorpekovnik/docker to maximum cleanliness, but the idea here is that the docker image will be updated each time your repo is. It should be usable like this: docker run igorpekovnik/lib ./compile.sh
|
BTW: Untested, and made the pull request because I've done this many times before. I am doing some testing now that includes the build automation, and will let you know the results. |
|
Image creation needs access to loop devices, so it will require running docker in privileged mode (if I understand its documentation correctly) |
|
Thank you! I'll get that added. I may try using something like wercker to deal with the image build automation so that it isn't as ugly as it is at the moment. |
Build: docker build --name lib . Invocation: docker run lib --privileged -it -P
|
Dockerfile now works, going to do a vagrantfile, too, because why not? |
|
Well, let's try. |
|
The next step in using this is for you or another (if there are any) of the repository's owners to go to hub.docker.com and then login, click "create automated build" in the upper-right hand corner, and then select the repository. This will make it so that a new docker image will be created each time the code for lib is updated :). |
|
Can also look into using something like wercker to create a more complex build chain. Here's how to use it before making the automated build: If you want to use this Docker image on ARM (not supported @ docker hub for automated builds) just change the first line: to Once this image is added as an automated build, you'll be able to run it like this: Note: I haven't come up with an awesome way to pull the output out of the docker image. I may add some volumes so that it's easier. For now you can use docker copy, etc.... |
|
Note: Looking for feedback on this! |
It's a file that will allow lib to run outside of its happy native debian environment, for example, on arch, or in fact... anywhere. That should actually do it, that single line. I can make it more complicated if need be, but I think that will work..... wait wait wait, have to do something about the path relativity, so..... I had it clone the repository anyway instead of just using the files that Docker will automatically copy over. May want to put this in igorpekovnik/docker to maximum cleanliness, but the idea here is that the docker image will be updated each time your repo is. It should be usable like this: