[{"_1":2,"_160":-5,"_161":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_139":140},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_128":-5,"_129":11,"_130":21,"_131":11,"_132":-5,"_133":11,"_134":-5,"_135":136,"_137":91,"_138":-7},"canonicalUrl","https://hub.docker.com/r/layoric/docker-geoserver/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","layoric","reponame","docker-geoserver","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2019-11-14T23:46:52.772517Z","description","","is_private","last_updated","2019-11-14T23:52:55.138815Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",184,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# docker-geoserver\n\nA simple docker container that runs GeoServer influenced by this docker\nrecipe: https://github.com/eliotjordan/docker-geoserver/blob/master/Dockerfile\n\n## Getting the image\n\nThere are various ways to get the image onto your system:\n\nThe preferred way (but using most bandwidth for the initial image) is to\nget our docker trusted build like this:\n\n```shell\ndocker pull kartoza/geoserver\n```\n\n### To build yourself with a local checkout using the build script:\n\nEdit the build script to change the following variables:\n\n- The variables below represent the latest stable release you need to build. i.e 2.15.2\n\n ```text\n BUGFIX=2\n MINOR=15\n MAJOR=2\n ```\n\n```shell\ngit clone git://github.com/kartoza/docker-geoserver\ncd docker-geoserver\n./build.sh\n```\n\nEnsure that you look at the build script to see what other build arguments you can include whilst building your image.\n\nIf you do not intend to jump between versions you need to specify that in the build script.\n\n### Building with war file from a URL\n\nIf you need to build the image with a custom GeoServer war file that will be downloaded from a server, you\ncan pass the war file url as a build argument to docker, example:\n\n```shell\ndocker build --build-arg WAR_URL=http://download2.nust.na/pub4/sourceforge/g/project/ge/geoserver/GeoServer/2.13.0/geoserver-2.13.0-war.zip --build-arg GS_VERSION=2.13.0\n```\n\n**Note: war file version should match the version number provided by `GS_VERSION` argument otherwise we will have a mismatch of plugins and GeoServer installed.**\n\n### Building with Oracle JDK\n\nDownload `jdk-8u201-linux-x64.tar.gz` or the latest version from [Oracle Java](https://www.oracle.com) and save the contents into\nthe resources folder. This used to be done by the setup scripts but no longer works due to the changes\nin the licencing terms from Oracle which require users to login to their site.\n\nTo replace OpenJDK Java with the Oracle JDK, set build-arg `ORACLE_JDK=true`:\n\n```shell\ndocker build --build-arg ORACLE_JDK=true --build-arg GS_VERSION=2.13.0 -t kartoza/geoserver .\n```\n\n### Building with plugins\n\nInspect setup.sh to confirm which plugins (community modules or standard plugins) you want to include in\nthe build process, then add them in their respective sections in the script.\n\nYou should ensure that the plugins match the version for the GeoServer WAR zip file.\n\n### Removing Tomcat extras during build\n\nTo remove Tomcat extras including docs, examples, and the manager webapp, set the\n`TOMCAT_EXTRAS` build-arg to `false`:\n\n```shell\ndocker build --build-arg TOMCAT_EXTRAS=false --build-arg GS_VERSION=2.13.0 -t kartoza/geoserver .\n```\n\n### Building with specific version of Tomcat\n\nTo build using a specific tagged release for tomcat image set the\n`IMAGE_VERSION` build-arg to `8-jre8`: See the [dockerhub tomcat](https://hub.docker.com/_/tomcat/)\nto choose which tag you need to build against.\n\n```shell\ndocker build --build-arg IMAGE_VERSION=8-jre8 --build-arg GS_VERSION=2.13.0 -t kartoza/geoserver:2.13.0 .\n```\n\n### Building with file system overlays (advanced)\n\nThe contents of `resources/overlays` will be copied to the image file system\nduring the build. For example, to include a static Tomcat `setenv.sh`,\ncreate the file at `resources/overlays/usr/local/tomcat/bin/setenv.sh`.\n\nYou can use this functionality to write a static GeoServer directory to\n`/opt/geoserver/data_dir`, include additional jar files, and more.\n\nOverlay files will overwrite existing destination files, so be careful!\n\n#### Build with CORS Support\n\nThe contents of `resources/overlays` will be copied to the image file system\nduring the build. For example, to include a static web xml with CORS support `web.xml`,\ncreate the file at `resources/overlays/usr/local/tomcat/conf/web.xml`.\n\n## Run (manual docker commands)\n\n**Note:** You probably want to use docker-compose for running as it will provide\na repeatable orchestrated deployment system.\n\nYou probably want to also have PostGIS running too. To create a running\ncontainer do:\n\n```shell\ndocker run --name \"postgis\" -d -t kartoza/postgis:9.4-2.1\ndocker run --name \"geoserver\" --link postgis:postgis -p 8080:8080 -d -t kartoza/geoserver\n```\n\nYou can also use the following environment variables to pass a\nuser name and password to PostGIS:\n\n* `-e USERNAME=`\n* `-e PASS=`\n\nYou can also use the following environment variables to pass arguments to GeoServer:\n\n* `GEOSERVER_DATA_DIR=`\n* `ENABLE_JSONP=`\n* `MAX_FILTER_RULES=`\n* `OPTIMIZE_LINE_WIDTH=`\n* `FOOTPRINTS_DATA_DIR=`\n* `GEOWEBCACHE_CACHE_DIR=`\n* `GEOSERVER_ADMIN_PASSWORD=`\n* Tomcat properties:\n\n * You can change the variables based on [geoserver container considerations](http://docs.geoserver.org/stable/en/user/production/container.html). These arguments operate on the `-Xms` and `-Xmx` options of the Java Virtual Machine\n * `INITIAL_MEMORY=` : Initial Memory that Java can allocate, default `2G`\n * `MAXIMUM_MEMORY=` : Maximum Memory that Java can allocate, default `4G`\n\n**Note:**\n\n### Changing GeoServer password on runtime\n\nThe default GeoServer user is 'admin' and the password is 'geoserver'. You can pass the environment variable\nGEOSERVER_ADMIN_PASSWORD to change it on runtime.\n\n```shell\ndocker run --name \"geoserver\" -e GEOSERVER_ADMIN_PASSWORD=myawesomegeoserver -p 8080:8080 -d -t kartoza/geoserver\n```\n\n## Run (automated using docker-compose)\n\nWe provide a sample ``docker-compose.yml`` file that illustrates\nhow you can establish a GeoServer + PostGIS + GeoGig orchestrated environment\nwith nightly backups that are synchronised to your backup server via btsync.\n\nIf you are **not** interested in the backups, GeoGig and btsync options, comment\nout those services in the ``docker-compose.yml`` file.\n\nIf you start the stack using the compose file make sure you login into GeoServer using username:`admin`\nand password:`myawesomegeoserver` as specified by the env file `geoserver.env`\n\nPlease read the ``docker-compose``\n[documentation](https://docs.docker.com/compose/) for details\non usage and syntax of ``docker-compose`` - it is not covered here.\n\nIf you **are** interested in btsync backups, install [Resilio sync]\non your desktop NAS or other backup destination and create two\nfolders:\n\n* one for database backup dumps\n* one for geoserver data dir\n\nThen make a copy of each of the provided EXAMPLE environment files e.g.:\n\n```shell\ncp docker-env/btsync-db.env.EXAMPLE docker-env/btsync-db.env\ncp docker-env/btsync-media.env.EXAMPLE docker-env/btsync-media.env\n```\n\nThen edit the two env files, placing your Read/Write Resilio keys\nin the place provided.\n\nTo run the example do:\n\n```shell\ndocker-compose up\n```\n\nWhich will run everything in the foreground giving you the opportunity\nto peruse logs and see that everything spins up nicely.\n\nOnce all services are started, test by visiting the GeoServer landing\npage in your browser: [http://localhost:8600/geoserver](http://localhost:8600/geoserver).\n\nTo run in the background rather, press ``ctrl-c`` to stop the\ncontainers and run again in the background:\n\n```shell\ndocker-compose up -d\n```\n\n**Note:** The ``docker-compose.yml`` **uses host based volumes** so\nwhen you remove the containers, **all data will be kept**. Using host based volumes\n ensures that your data persists between invocations of the compose file. If you need\n to delete the container data you need to run `docker volume prune`. Pruning the volumes will\n remove all the storage volumes that are not in use so users need to be careful of such a move.\n Either set up btsync (and test to verify that your backups are working, we take\n**no responsibility** if the examples provided here do not produce\na reliable backup system).\n\n## Run (automated using rancher)\n\nAn even nicer way to run the examples provided is to use our Rancher\nCatalogue Stack for GeoServer. See [http://rancher.com](http://rancher.com)\nfor more details on how to set up and configure your Rancher\nenvironment. Once Rancher is set up, use the Admin -> Settings menu to\nadd our Rancher catalogue using this URL:\n\nhttps://github.com/kartoza/kartoza-rancher-catalogue\n\nOnce your settings are saved open a Rancher environment and set up a\nstack from the catalogue's 'Kartoza' section - you will see\nGeoServer listed there.\n\nIf you want to synchronise your GeoServer settings and database backups\n(created by the nightly backup tool in the stack), use [Resilio\nsync](https://www.Resilio.com/) to create two Read/Write keys:\n\n* one for database backups\n* one for GeoServer media backups\n\n**Note:** Resilio sync is not Free Software. It is free to use for\nindividuals. Business users need to pay - see their web site for details.\n\nYou can try a similar approach with Syncthing or Seafile (for free options)\nor Dropbox or Google Drive if you want to use another commercial product. These\nproducts all have one limitation though: they require interaction\nto register applications or keys. With Resilio Sync you can completely\nautomate the process without user intervention.\n\n## Storing data on the host rather than the container.\n\nDocker volumes can be used to persist your data.\n\nIf you need to use geoserver data directory that contains sample examples and configurations download\nit from [geonode](http://build.geonode.org/geoserver/latest/) site as indicated below:\n\n```shell\n\n# Example - ${GS_VERSION} is the geoserver version i.e 2.13.0\nwget http://build.geonode.org/geoserver/latest/data-2.13.x.zip\nunzip data-2.13.x.zip -d ~/geoserver_data\ncp scripts/controlflow.properties ~/geoserver_data\nchmod -R a+rwx ~/geoserver_data\ndocker run -d -p 8580:8080 --name \"geoserver\" -v $HOME/geoserver_data:/opt/geoserver/data_dir kartoza/geoserver:${GS_VERSION}\n```\n\nCreate an empty data directory to use to persist your data.\n\n```shell\nmkdir -p ~/geoserver_data && chmod -R a+rwx ~/geoserver_data\ndocker run -d -v $HOME/geoserver_data:/opt/geoserver/data_dir kartoza/geoserver\n```\n\n### Control flow properties\n\nThe control flow module is installed by default and it is used to manage request in geoserver. In order\nto customise it based on your resources and use case read the instructions from\n[documentation](http://docs.geoserver.org/latest/en/user/extensions/controlflow/index.html). Modify\nthe file scripts/controlflow.properties before building the image.\n\n## Credits\n\n* Tim Sutton (tim@kartoza.com)\n* Shane St Clair (shane@axiomdatascience.com)\n* Alex Leith (alexgleith@gmail.com)\n* Admire Nyakudya (admire@kartoza.com)\n* Gavin Fleming (gavin@kartoza.com)\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",358758603,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},"content_type","creator",739666,"full_size",358731517,"id",76414815,"images",[101],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},"architecture","amd64","digest","sha256:36f039e937fee09663190736674b1b9de34f26fcfc541ae33a73843f81edf62a","features","last_pulled","2026-09-30T11:48:30.084296221Z","last_pushed","2019-11-14T23:52:55Z","os","linux","os_features","os_version","size","variant","2019-11-14T23:52:54.802196Z","last_updater","last_updater_username","media_type","latest","repository",8021417,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":141,"_148":149,"_135":158,"_159":11},{"_40":142,"_42":143,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":144,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":145,"_79":11,"_80":147,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":146},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_150":64,"_151":-5,"_152":-5,"_153":154},"count","next","previous","results",[155],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":156,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},[157],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},[],"canDeleteTags","actionData","errors"]

layoric/docker-geoserver

Tags for layoric/docker-geoserver