Skip to content

EOFarm/docker-mapserver

 
 

Repository files navigation

Docker image for Mapserver

Here is a sample Dockerfile for using it:

FROM camptocamp/mapserver

COPY *.map /etc/mapserver/
COPY *.sh *.env /docker-entrypoint.d/

The main mapfile should be /etc/mapserver/mapserver.map.

Or you can use the image as is and mount volumes to customize it.

Only tags for minor releases exist, not tag for bug fixes.

If the container is run as root, apache listens on port 80. If it is run as another user, it listens on port 8080.

Tunings

All the bash snipets in /docker-entrypoint.d ending with .env will be sourced.

All the executable files in /docker-entrypoint.d ending with .sh will be executed by the default entrypoint.

All the files ending with .tmpl in /etc/mapserver and /etc/apache2 (can be changed by defining CONFD_DIRS in one of the sourced files) will go though confd with the env backend. The TOML files are created automagically to create a file at the same location, with just the .tmpl extension removed.

You can use the following environment variables (when starting the container) to tune it:

  • MS_DEBUGLEVEL: The debug level 0=off 5=verbose
  • MS_ERRORFILE: If you want the debug to something other than STDOUT
  • MAX_REQUESTS_PER_PROCESS: To work around memory leaks (defaults to 1000)
  • MIN_PROCESSES: The minimum number of fcgi processes to keep (defaults to 1)
  • MAX_PROCESSES: The maximum number of fcgi processes to keep (defaults to 5)
  • MAPSERVER_CATCH_SEGV: Set to 1 to have the stacktraces in case of crash
  • LISTEN_PORT_80: When running the container as an unprivileged user, apache will listen to port 8080 instead of 80. Set to 1 force listening to port 80 instead.
  • BUSY_TIMEOUT: The maximum time limit for request handling (defaults to 300)
  • IDLE_TIMEOUT: Application processes which have not handled a request for this period of time will be terminated (defaults to 300)
  • IO_TIMEOUT: The maximum period of time the module will wait while trying to read from or write to a FastCGI application (defaults to 40)

Running multiple mapfiles

This section is for if you would like to use more than one mapfile, or use a mapfile that isn't /etc/mapserver/mapserver.map.

In this example we have two mapfiles we want to use that both reference data in different directories. My mapfiles are wms.map and wfs.map and are located in /mapfiles/ on the host, and the data for these mapfiles is located in the host in the directory /mapdata/wms and /mapdata/wfs.

docker run -d \
        --restart=unless-stopped \
        --volume=/mapfiles/wms.map/:/etc/mapserver/wms.map:ro \
        --volume=/mapfiles/wfs.map/:/etc/mapserver/wfs.map:ro \
        --volume=/mapdata/wms/:/mapdata/wms/:ro \
        --volume=/mapdata/wfs/:/mapdata/wfs/:ro \
        camptocamp/mapserver

For accessing maps for the "wfs" service add map=/etc/mapserver/wfs.map to your query string. Here is the URL for a "GetCapabilities" request:

http://your.mapserver.host/?map=/etc/mapserver/wfs.map&service=WFS&request=GetCapabilities

Similarly, for accessing maps for the "wms" service add map=/etc/mapserver/wms.map to your query string.

Project version

Packages

No packages published

Languages

  • Dockerfile 38.6%
  • Python 27.2%
  • Shell 23.1%
  • Makefile 11.1%