| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| public:docker [2017-02-21 14:21] – Jan David Mol | public:docker [2017-03-08 15:27] – external edit 127.0.0.1 |
|---|
| |
| ===== Development (extending the software) ===== | ===== Development (extending the software) ===== |
| | |
| | === Q: How do I obtain your Dockerfiles? === |
| | |
| | A: By running: |
| | |
| | <file> |
| | svn co -N https://svn.astron.nl/LOFAR/branches/LOFAR-Release-2_19/ |
| | cd LOFAR-Release-2_19 |
| | mkdir -p build/gnu_opt && cd build/gnu_opt |
| | |
| | cmake ../.. -DBUILD_PACKAGES=Docker -DUSE_LOG4CPLUS=OFF && make -j 16 install |
| | </file> |
| | |
| | which will put the Dockerfiles in subdirectories in ''LOFAR-Release-2_19/build/gnu_opt/installed/share/docker''. |
| |
| === Q: How do I add files/modifications permanently? === | === Q: How do I add files/modifications permanently? === |
| </file> | </file> |
| |
| Finally, you run ''docker build -t myimage:mytag directory/'' where ''directory'' is the directory containing the Dockerfile, and ''myimage:mytag'' is the name and tag of your new image (instead of ''lofar-pipeline:LOFAR-Release-2_19''). See also the [[https://docs.docker.com/engine/reference/builder/|Docker manual]] on how to make and use Dockerfiles. | Finally, you run <file>docker build -t myimage:mytag directory/</file> where ''directory'' is the directory containing the Dockerfile, and ''myimage:mytag'' is the name and tag of your new image (instead of ''lofar-pipeline:LOFAR-Release-2_19''). See also the [[https://docs.docker.com/engine/reference/builder/|Docker manual]] on how to make and use Dockerfiles. |
| |
| === Q: How do I add initialisation stuff? (PYTHONPATH, etc) === | === Q: How do I add initialisation stuff? (PYTHONPATH, etc) === |
| A: Our Docker images execute ''/opt/bashrc'' upon entry, which in turn reads and sources all the files in ''/opt/bashrc.d/'' in order. You can thus add bash files to this directory that contain your initialisation statements, f.e. a file called ''20-myextension'' containing ''export PYTHONPATH=$PYTHONPATH:/opt/my_extension''. | A: Our Docker images execute ''/opt/bashrc'' upon entry, which in turn reads and sources all the files in ''/opt/bashrc.d/'' in order. You can thus add bash files to this directory that contain your initialisation statements, f.e. a file called ''20-myextension'' containing ''export PYTHONPATH=$PYTHONPATH:/opt/my_extension''. |
| |
| Note: if you add eggs to the image, you need to put the egg /filename/ to the PYTHONPATH. It is not enough to add the directory containing the egg. | Note: if you add eggs to the image, you need to put the egg //filename// to the PYTHONPATH. It is not enough to add the directory containing the egg. |