[Koha-devel] ktd and persistent data

januszop at gmail.com januszop at gmail.com
Sat Sep 16 00:42:02 CEST 2023


Hi All,

This is (probably) my first post on this list. I had the pleasure of meeting
some of you recently in Helsinki (and before that in Dublin in 2019). I live
in Krakow, Poland and take care of several Koha installations in
medium-sized scientific and theological libraries. Much of my time is spent
analyzing and correcting bibliographic data. However, if my libraries
encounter any problems in Koha, I try to report them in Bugzilla and, if
possible, provide patches as well (I sent the first official patch in 2011).
Sometimes I don't have enough patience or time and I patch problems locally
(forgive me, I feel guilty here)...

The Helsinki meeting encouraged me to use ktd more intensively. Here,
however, I run into a problem trying to use persistent data (kp command as
described at
https://gitlab.com/koha-community/koha-testing-docker/-/wikis/Koha-Testing-D
ocker). Docker creates the koha_db-data volume as expected. However, after
shutting down the test environment (with kd command), when trying to run it
again (kp), the koha container does not start properly -- it ends with the
message:

Database is not empty! at /kohadevbox/misc4dev/populate_db.pl line 103.

Indeed, the populate_db.pl script is executed unconditionally when starting
this container. 

Question: what am I doing wrong or what did I not understand? What should be
the scheme of working with persistent data?

I would appreciate a hint.

Greetings,
Janusz



More information about the Koha-devel mailing list