Hi all,
I just added a Dockerfile to the Subversion repository. The Dockerfile uses the local source code, i.e. typically what you get with svn, because it is a part of the source code. It it not downloading any GRASS GIS source code by itself, so you can make changes in the source code locally and rebuild the image (you need to tell Docker to remove the existing image (layer) or to not use cache).
It is using Ubuntu, but something more lightweight may be more appropriate, some other images, on the other hand, may bring some additional features. It is not installing any GRASS addons or using PPA repositories.
The documentation is in the README (yes, we have a README file ;-). I hope it is the right place. It contains example which runs all the tests. It assumes you have NC SPM location on your (local) disk.
The image keeps the source code (the source code is not removed) and it has one volume which you mount and that’s where the data are supposed to be.
Please, send the feedback here. Let me know if it fits your use cases and open tickets if you have some requests.
Vaclav
[Using the thread with the announcement for this answer.]
···
On Sat, Jul 29, 2017 at 12:15 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
Hi all,
I just added a Dockerfile to the Subversion repository. The Dockerfile uses the local source code, i.e. typically what you get with svn, because it is a part of the source code. It it not downloading any GRASS GIS source code by itself, so you can make changes in the source code locally and rebuild the image (you need to tell Docker to remove the existing image (layer) or to not use cache).
It is using Ubuntu, but something more lightweight may be more appropriate, some other images, on the other hand, may bring some additional features. It is not installing any GRASS addons or using PPA repositories.
The documentation is in the README (yes, we have a README file ;-). I hope it is the right place. It contains example which runs all the tests. It assumes you have NC SPM location on your (local) disk.
The image keeps the source code (the source code is not removed) and it has one volume which you mount and that’s where the data are supposed to be.
Please, send the feedback here. Let me know if it fits your use cases and open tickets if you have some requests.
Vaclav
Thanks for the Dockerfile, Vaclav!
On Sun, Jul 30, 2017 at 1:11 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
[Using the thread with the announcement for this answer.]
...
It is the Dockerfile. You let Docker build a Docker image using that file
(Docker looks to the directory specified and finds the Dockerfile, kind of
like make and Makefile). You then use Docker to run a process in the
container derived from that image. GRASS GIS is build as part of building of
the image. See the readme file for examples:
https://trac.osgeo.org/grass/browser/grass/trunk/README#L53
what do you think of the suggested changes?
https://lists.osgeo.org/pipermail/grass-dev/2017-July/085633.html
I attach the modified Dockerfile which I tested on Fedora (still
creating the Ubuntu docker image). Appears to work fine.
Markus
(attachments)
Dockerfile.diff (639 Bytes)
On Mon, Aug 7, 2017 at 6:35 PM, Markus Neteler <neteler@osgeo.org> wrote:
Thanks for the Dockerfile, Vaclav!
On Sun, Jul 30, 2017 at 1:11 AM, Vaclav Petras <wenzeslaus@gmail.com>
wrote:
> [Using the thread with the announcement for this answer.]
...
> It is the Dockerfile. You let Docker build a Docker image using that file
> (Docker looks to the directory specified and finds the Dockerfile, kind
of
> like make and Makefile). You then use Docker to run a process in the
> container derived from that image. GRASS GIS is build as part of
building of
> the image. See the readme file for examples:
>
> https://trac.osgeo.org/grass/browser/grass/trunk/README#L53
what do you think of the suggested changes?
https://lists.osgeo.org/pipermail/grass-dev/2017-July/085633.html
I attach the modified Dockerfile which I tested on Fedora (still
creating the Ubuntu docker image). Appears to work fine.
If that works with the Docker image, I'm for it. I'm just not sure about
pthreads. The fact that r.mapcalc is not using them does not mean that some
addon module won't use them (and thus need them in the configuration). I'm
afraid the package list is originally from some other source, like the wiki.
On Sat, Jul 29, 2017 at 6:15 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
Hi all,
I just added a Dockerfile to the Subversion repository. The Dockerfile uses
the local source code, i.e. typically what you get with svn, because it is a
part of the source code. It it not downloading any GRASS GIS source code by
itself, so you can make changes in the source code locally and rebuild the
image (you need to tell Docker to remove the existing image (layer) or to
not use cache).
It is using Ubuntu, but something more lightweight may be more appropriate,
some other images, on the other hand, may bring some additional features. It
is not installing any GRASS addons or using PPA repositories.
The documentation is in the README (yes, we have a README file ;-). I hope
it is the right place. It contains example which runs all the tests. It
assumes you have NC SPM location on your (local) disk.
The image keeps the source code (the source code is not removed) and it has
one volume which you mount and that's where the data are supposed to be.
Now available on docker hub:
docker pull neteler/grassgis7
Markus