How can I run geoserver nightly on Docker?

GeoServer GeoServer User
1

The documentation mentions pulling “docker.osgeo.org/geoserver:2.27.x”, but that’s just a placeholder. I’ve tried “2.27.0”, “2.27-SNAPSHOT”, “main”, and other tags but to no avail. Which tag do I need to use? I need some community plugins so I need geoserver nightly.

1 Like
2

Welcome to the forum. I do not think that is a placeholder? For blog post I tested the following:

docker pull docker.osgeo.org/geoserver:2.27.x
docker run -it -p8081:8080 docker.osgeo.org/geoserver:2.27.x

However that does not appear to be working today:

Error response from daemon: manifest for docker.osgeo.org/geoserver:2.27.x not found: manifest unknown: manifest unknown

Looking at instructions that appears correct.

Testing an earlier version is working for me:

docker pull docker.osgeo.org/geoserver:2.26.x
docker run -it -p8080:8080 \
  --env INSTALL_EXTENSIONS=true \
  --env COMMUNITY_EXTENSIONS="ogcapi-features" \                               
  docker.osgeo.org/geoserver:2.26.x

And I can see the community module on the welcome page:

image
image1678×352 27.4 KB

And in the module rest/about/manifest:

image
image1282×1062 97.5 KB

3

So the question is why is 2.27.x not working?

Checking geoserver-release-docker #1325 [Jenkins] it has built recently:

Started by upstream project geoserver-main-nightly
(geoserver-main-nightly [Jenkins]) build number 1966
originally caused by:

  • Started by upstream project geoserver-main build number 2100
    originally caused by:
    • Started by an SCM change

Checking the logs we can see:

Login Succeeded
docker push geoserver-docker.osgeo.org/geoserver:2.25.x

That is … not so good!

Bug report: GEOS-11572 Docker main published as 2.25.x

4

So I understand that a recent build mistake pushed 2.27.x as 2.25.x? Indeed, that’s not ideal. However, running 2.25.0 runs, well, 2.25.0, and I still can’t use community modules. Do you have suggestions that I can follow while 2.27.x is getting fixed?

5

Yes, please run 2.26.x which is the nightly build of the stable series.
I used it in the examples above (so you can copy and paste).

6

A few heads up for folks who found this thread and want the full solution (these conclusions are based on my local testing, I’m not a GeoServer expert):

  • 2.26.x, where ‘x’ is the character ‘x’, is a nightly build. 2.26.x, where ‘x’ is an integer, is stable, and “COMMUNITY_EXTENSIONS” will be ignored.

Thanks for your help, Jody.

7

I am not sure I understand the second point about /opt ? Can you explain what happens …

8

I was about to write that the container didn’t seem to install COMMUNITY_EXTENSION when the /opt/geoserver_data folder is already initialized, but I couldn’t reproduce what happened. It was probably a misconfiguration on my part, so I’ll go tweak my previous answer.

9

I was able to fix the issue with 2.27.x nightly not working.

GEOS-11572: There is a small fix to correct the documentation example still wanting review.

But the important thing is you can now try out the latest OGC API - Features extension:

docker pull docker.osgeo.org/geoserver:2.27.x
docker run -it -p8080:8080 \\
        --env INSTALL_EXTENSIONS=true \\
        --env STABLE_EXTENSIONS="ogcapi-features" \\
        docker.osgeo.org/geoserver:2.27.x