A vanilla CKAN instance. Very simple customisations possible using environment variables. Intended primarily as a base for extension.
1.1K
This image contains a vanilla configuration of CKAN. You can use this image as-is if you specify the location of a Postgres database and a Solr core on startup:
docker run -i -t -p 80 \
-e DATABASE_URL=postgres://user:pass@hostname/db \
-e SOLR_URL=http://hostname:8983/solr/ckan_default \
nickstenning/ckan:2.2
This will run CKAN, connect to the database, and initialise it if need be. Configuring Solr will have to be done separately. There are a couple of other environment variables you can use to customise the deployment, including GUNICORN_NUM_WORKERS and ERROR_EMAIL, which do what you might expect.
Alternatively, and perhaps more realistically you can use this image as a base for extension. If a
configuration file is injected to /etc/ckan/default.ini, the image will use that and ignore the DATABASE_URL, SOLR_URL, and ERROR_EMAIL environment variables. (GUNICORN_NUM_WORKERS is still used.)
A minimal Dockerfile that use this image as a base might look something like this:
FROM nickstenning/ckan:2.2
ADD ./mycustomconfig.ini /etc/ckan/default.ini
Lastly, the CKAN file store is at /var/lib/ckan, and in a production environment you would almost certainly mount this data volume outside the running container:
docker run ... -v /mnt/storage:/var/lib/ckan ...
Content type
Image
Digest
sha256:18b6aa40c…
Size
302.5 MB
Last updated
almost 11 years ago
docker pull nickstenning/ckan