Hi Waylon,
I am running Koha from debian stretch slim container (with a mariadb container
based on Ubuntu).
For Koha choosing Debian is always safer.
I had to allow two kernel privileges to get things working at 'docker run' time
to start the Koha container:
--cap-add=SYS_NICE --cap-add=DAC_READ_SEARCH
Hope that helps,
Marcel
________________________________
Van: koha-devel-boun...@lists.koha-community.org
<koha-devel-boun...@lists.koha-community.org> namens Waylon Robertson
<wrobertson1...@yahoo.co.nz>
Verzonden: donderdag 18 april 2019 03:26:31
Aan: koha-devel@lists.koha-community.org
Onderwerp: [Koha-devel] koha-testing-docker - production use
I am trying to move my already existing 17.05 koha install, on a old
ubuntu-minimal docker, to koha-testing-docker, figure all it needs is a change
of config, and then i can stop the db docker container, only... it is ignoring
my changes to koha-conf.xml inside sites/kohadev.
my changes are there, and yet koha-rebuild-zebra etc are just ignoring them.
I've also tried changing .env and defaults.env to match my creds before
docker-compose up, and it seems like all options are taken into account, except
the HOSTNAME, or DB_HOSTNAME or DB_HOST
no variation works.
I am thinking, maybe its better to just start from a debian docker image, and
start from there, build it up myself?
I need to do this, as the docker i have, won't boot up on my new centos 7
system, mpm_itk says something about seccomp, and stops apache from running
perl.
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
