[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grass-user
Subject:    Re: [GRASS-user] Minimal docker file to create an image for an R script which calls GRASS functions
From:       Mehrdad Varedi <varedi () waterlix ! com>
Date:       2020-05-10 17:25:53
Message-ID: CACoeB3pfk12NvoHtsGJJGzJJco0u6xu97rBvWjpsN-wAXO9GMA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thanks Markus, I'll check it out.
Mehrdad

On Sun, May 10, 2020 at 8:07 AM Markus Neteler <neteler@osgeo.org> wrote:

> Hi Mehrdad,
>
> On Sun, May 10, 2020 at 9:25 AM Mehrdad Varedi <varedi@waterlix.com>
> wrote:
> >
> > Hi Everyone,
> >
> > I am interested in deploying an R shiny app in the form of a docker
> image.
> >
> > The Shiny App uses GRASS functions and I am wondering how shall I
> package GRASS and R together in a docker file to create an image. Just a
> simple example to make it work is what I want.
> >
> > If you are aware of how I can optimize the integration with GRASS. like
> having GRASS and R script in separate containers although still being able
> to call GRASS functions from the R container, that would be great.
>
> The smallest GRASS GIS (7.8) docker file I am aware of is our
> multi-stage image which is Alpine based.
> It is of 320 MB, Python 3 based and PDAL included:
>
> https://hub.docker.com/r/mundialis/grass-py3-pdal
>
> (yes, the README is still to be updated).
>
> docker pull mundialis/grass-py3-pdal
>
> Maybe you could start with that?
>
> Best,
> Markus
>
>
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
>

[Attachment #5 (text/html)]

<div dir="ltr"><div>Thanks Markus, I&#39;ll check it \
out.</div>Mehrdad<br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sun, May 10, 2020 at 8:07 AM Markus Neteler &lt;<a \
href="mailto:neteler@osgeo.org">neteler@osgeo.org</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi Mehrdad,<br> <br>
On Sun, May 10, 2020 at 9:25 AM Mehrdad Varedi &lt;<a \
href="mailto:varedi@waterlix.com" target="_blank">varedi@waterlix.com</a>&gt; \
wrote:<br> &gt;<br>
&gt; Hi Everyone,<br>
&gt;<br>
&gt; I am interested in deploying an R shiny app in the form of a docker image.<br>
&gt;<br>
&gt; The Shiny App uses GRASS functions and I am wondering how shall I package GRASS \
and R together in a docker file to create an image. Just a simple example to make it \
work is what I want.<br> &gt;<br>
&gt; If you are aware of how I can optimize the integration with GRASS. like having \
GRASS and R script in separate containers although still being able to call GRASS \
functions from the R container, that would be great.<br> <br>
The smallest GRASS GIS (7.8) docker file I am aware of is our<br>
multi-stage image which is Alpine based.<br>
It is of 320 MB, Python 3 based and PDAL included:<br>
<br>
<a href="https://hub.docker.com/r/mundialis/grass-py3-pdal" rel="noreferrer" \
target="_blank">https://hub.docker.com/r/mundialis/grass-py3-pdal</a><br> <br>
(yes, the README is still to be updated).<br>
<br>
docker pull mundialis/grass-py3-pdal<br>
<br>
Maybe you could start with that?<br>
<br>
Best,<br>
Markus<br>
<br>
<br>
<br>
-- <br>
Markus Neteler, PhD<br>
<a href="https://www.mundialis.de" rel="noreferrer" \
target="_blank">https://www.mundialis.de</a> - free data with free software<br> <a \
href="https://grass.osgeo.org" rel="noreferrer" \
target="_blank">https://grass.osgeo.org</a><br> <a \
href="https://courses.neteler.org/blog" rel="noreferrer" \
target="_blank">https://courses.neteler.org/blog</a><br> </blockquote></div>


[Attachment #6 (text/plain)]

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic