You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, they have not been modified over 4 years, and only seem to be leftover and unused code.
This should be removed entirely, as it causes unnecessary confusion about which GeoServer is employed, as well as causing many (>50 critical, >160 high) vulnerabilities to be reflected by security scans due to very old references.
A much more up-to-date and reduced set of security vulnerabilities (~4 critical with pavics/geoserver:2.22.2) is detailed in #320 (note that this is still not the latest active version in the stack still using pavics/geoserver:2.19.0).
- Delete unused Dockerfiles, fixes#349 and fixes#352
* birdhouse/docker/geoserver: not used since 3-4 years, replaced by
https://github.com/kartoza/docker-geoserver
* birdhouse/config/geoserver/Dockerfile: was introduced in commit
f3b9896 (PR #233, merge commit
d1ecc63) as a temporary solution only,
not needed with newer kartoza docker images.
- Move birdhouse/docker/solr to
birdhouse/deprecated-components/solr/docker to group related files
together. Solr has been deprecated since PR #311 (merge commit
a8d3612).
Description
Some Docker references for GeoServer are specified here:
https://github.com/bird-house/birdhouse-deploy/tree/master/birdhouse/docker/geoserver
However, they have not been modified over 4 years, and only seem to be leftover and unused code.
This should be removed entirely, as it causes unnecessary confusion about which GeoServer is employed, as well as causing many (>50 critical, >160 high) vulnerabilities to be reflected by security scans due to very old references.
The active GeoServer in the stack is referenced with the following file instead:
https://github.com/bird-house/birdhouse-deploy/blob/master/birdhouse/config/geoserver/Dockerfile
A much more up-to-date and reduced set of security vulnerabilities (~4 critical with
pavics/geoserver:2.22.2
) is detailed in #320 (note that this is still not the latest active version in the stack still usingpavics/geoserver:2.19.0
).References
Concerned Organizations
All using GeoServer.
The text was updated successfully, but these errors were encountered: