Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saga plugin installation steps causing Docker build to fail #41

Closed
Robinlovelace opened this issue Sep 27, 2023 · 7 comments
Closed

Saga plugin installation steps causing Docker build to fail #41

Robinlovelace opened this issue Sep 27, 2023 · 7 comments

Comments

@Robinlovelace
Copy link
Contributor

With the following message:

Dockerfile:48
--------------------
  46 |     RUN sh -c 'echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/qgis-archive-keyring.gpg] https://qgis.org/ubuntugis `lsb_release -c -s` main" > /etc/apt/sources.list.d/qgis.list'
  47 |     RUN apt-get update
  48 | >>> RUN apt-get install -y qgis qgis-plugin-grass saga
  49 |     RUN wget -qO sagang_plugin.zip https://plugins.qgis.org/plugins/processing_saga_nextgen/version/0.0.7/download/
  50 |     RUN unzip -q sagang_plugin.zip -d /home/rstudio/.local/share/QGIS/QGIS3/profiles/default/python/plugins
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get install -y qgis qgis-plugin-grass saga" did not complete successfully: exit code: 100
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt-get install -y qgis qgis-plugin-grass saga" did not complete successfully: exit code: 100

Source: https://github.com/geocompx/docker/actions/runs/6321057960/job/17164486628#step:8:644

Relevant lines:

docker/qgis/Dockerfile

Lines 48 to 50 in 00f4c90

RUN apt-get install -y qgis qgis-plugin-grass saga
RUN wget -qO sagang_plugin.zip https://plugins.qgis.org/plugins/processing_saga_nextgen/version/0.0.7/download/
RUN unzip -q sagang_plugin.zip -d /home/rstudio/.local/share/QGIS/QGIS3/profiles/default/python/plugins

Any ideas @jannes-m ?

@nyalldawson
Copy link

Isn't it the apt-get step here which is failing, not anything to do with the saga plugin?

@florisvdh
Copy link

florisvdh commented Sep 27, 2023

Hi @Robinlovelace I saw your issue in the saga plugin.

My guess however is that you're installing QGIS from its ubuntugis repo (tailored to work with ubuntugis-unstable PPA; updated monthly or so), while two days ago GRASS has been updated in the PPA, typically breaking qgis-plugin-grass installation from QGIS repo. In the {qgisprocess} GHA workflow I therefore install QGIS from the ubuntugis-nightly-release repo, which is much quicker at levelling up with the PPA.

https://github.com/r-spatial/qgisprocess/blob/a88e665f6a9c960aba0e5f4bd6ca94d005676720/.github/workflows/R-CMD-check.yaml#L78C141-L78C141

@florisvdh
Copy link

florisvdh commented Sep 27, 2023

the ubuntugis-nightly-release repo, which is much quicker at levelling up with the PPA

But I think you'll have to wait a little longer; latest build there is 2023-09-23. https://ubuntu.qgis.org/ubuntu-nightly/pool/main/q/qgis/?C=M;O=D

@jannes-m
Copy link
Contributor

I am trying to build the image locally at the moment. And as @nyalldawson already mentionend, SAGA is not the problem. Instead an incompatible version of GRASS should be installed as already suspected by @florisvdh. Currently, I am using ubuntugis-nightly-release repo, let's see if this works out, probably not if the latest build is 2023-09-23. In any case, to avoid this issue in the future, let's switch to the ubuntugis-nightly-release.

@jannes-m
Copy link
Contributor

Locally, I could successfully build the container, so closing via 815c5a2.

@florisvdh
Copy link

florisvdh commented Sep 27, 2023

latest build there is 2023-09-23. https://ubuntu.qgis.org/ubuntu-nightly/pool/main/q/qgis/?C=M;O=D

I was looking in the wrong place here; that's the URL of Ubuntu-nightly, built against the Ubuntu GDAL etc, not against the PPA. Of course the URL must be https://ubuntugis.qgis.org/ubuntugis-nightly-release/pool/main/q/qgis/?C=M;O=D. Latest build there is from 2023-09-24 17:12 which indeed appears to work with current GRASS already 🚀 .

@Robinlovelace
Copy link
Contributor Author

Great job all, just checking this after busy day, stoked to see it's fixed. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants