digibib/koha-docker

Koha docker image builders

koha-docker's Issues

Docker unable to link mysql

tried
docker run --name Ma -d -e MYSQL_ROOT_PASSWORD="cic00" -e MYSQL_DATABASE="koha_koha" -e MYSQL_USER="koha" -e MYSQL_PASSWORD="Koha00" -p 3306:3306 mariadb

everything fine until i try to run koha
docker run -d --name Ko --cap-add=DAC_READ_SEARCH --cap-add=SYS_NICE --cap-add=MKNOD -p 6001:6001 -p 8080:8080 -p 8081:8081 -e KOHA_INSTANCE=koha -e KOHA_ADMINUSER=koha -e KOHA_ADMINPASS=cic48 -e SIP_WORKERS=3 --link Ma:koha_mysql -t digibib/koha:de6db3c5bee38241c55bf5cde588583858c77e16 0796a3450e4e0b2ac5f3e8d2b5432dc68b9c5d9b524ca01dff7c90989d8007a7

the log i got
Global config ... Setting up local cronjobs ... Setting up supervisord ... Mysql server setup ... Using linked mysql container Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface] [-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos] [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option] [-w deadline] [-W timeout] [hop1 ...] destination ERROR: Could not connect to remote mysql

also tried with mysql:5.6.20

Error while loading 3.pm: No such file or directory at (eval 19) line 4.

Hello,

I tried everything, but impossible to launch this docker image.
Exemple that i tried :
docker run --name kaoha_docker2 -p 6001:6001 -p 8080:8080 -p 8081:8081 -e KOHA_DBHOST=localhost -e KOHA_INSTANCE=kohainstance -e KOHA_ADMINUSER=admin -e KOHA_ADMINPASS=secret -e SIP_WORKERS=2 -e SIP_AUTOUSER1=autouser -e SIP_AUTOPASS1=autopass -t digibib/koha:latest

With or without options, I have this :

Global config ... creating dirs and permission for koha config and zebra index
Setting up supervisord ...
Mysql server setup ...
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.028 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.028/0.028/0.028/0.000 ms
Initializing local instance ...
Configuring local instance ...
Configuring SIPconfig.xml from templates and data from csv ...
Running db installer and applying local deichman mods - please be patient ...

2020-03-18 17:13:02,000 CRIT Supervisor running as root (no user in config file)
2020-03-18 17:13:02,008 INFO RPC interface 'supervisor' initialized
2020-03-18 17:13:02,008 INFO supervisord started with pid 23
2020-03-18 17:13:03,011 INFO spawned: 'syslog' with pid 26
2020-03-18 17:13:03,015 INFO spawned: 'privateApi' with pid 27
2020-03-18 17:13:03,019 INFO spawned: 'plack' with pid 28
2020-03-18 17:13:03,021 INFO spawned: 'sip' with pid 29
Fichier binaire (entrée standard) correspondant

And infinite loop of errors, CPU 8 cores 50% charged :

 Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
Error while loading 3.pm: No such file or directory at (eval 19) line 4.
...........................

I miss something ? I pass some hours in this issue, without any solutions...

Problem with run_webinstaller.pl?

The container is now running, but I can't access to Koha (either the OPAC or the intranet). I get a code 500 (Internal Server Error). When I check the logs, I can see the following in red:

ID: run_webinstaller
Function: cmd.script
Result: False
Comment:
Started: 12:21:45.371069
Duration: 366.781 ms
Changes:

What am I missing?

500 error after running the docker container

Hello, I followed both installation methods, in vagrant or standalone on my machine, basically :

• Docker pulled latest build
• docker run -d --name koha_docker -p 6001:6001 -p 8080:8080 -p 8081:8081 -t kohaimage:latest

When the container runs, I try to log on 192.168.33.10:8080 or 8081 (Which is the IP of the Vagrant Box), and I get a 500 error.

Could you help me please ?

Internal Server Error

Hi friends. Great work on getting this started, however I'm having some issues still.

Getting "Internal Server Error" upon login. Basically it recognizes perfectly if I have an incorrect username/password, but when I type in a correct username and password, it spits out an "Internal Server Error" every time. Im not sure where to go from here exactly. Any ideas?

Error while loading /etc/koha/plack.psgi

Hi,

i'm trying to run koha in docker. I'm using the letsencrypt-nginx-proxy-companion. I append the dockerfile

After starting docker and access the instance using a browser first i get

Sorry!
The Koha site you are trying to access is currently unavailable, probably because of maintenance. This is > not at all your fault, and we apologize for any inconvenience the downtime may cause you. Please check > back in a while. We hope to get things back up soon.

after a few settings i get

504 Gateway Time-out

The docker logs for koha give me:

koha                                 | Use of uninitialized value $home in concatenation (.) or string at /etc/koha  /plack.psgi line 54.
koha                                 | Use of uninitialized value $home in concatenation (.) or string at /etc/koha/plack.psgi line 58.
koha                                 | Use of uninitialized value $home in concatenation (.) or string at /etc/koha/plack.psgi line 74.
koha                                 | Error while loading /etc/koha/plack.psgi: Cannot find current script '/api/v1/app.pl' at /usr/share/perl5/Mojo/Server.pm line 48.

Launch gets 500 Internal Server Error

log: digibib-koha1.xlsx

Trying to test this guy out again, and I'm getting a 500 error out of the gate just launching the image as a container.
Something is going on with creating the mysql tables within the same image. I've tried linking it as well and had some luck with adding a standalone mysql container, but when I'd enter correct login credentials, it'd have an error.

Can't login to new instance

Using the docker hub tag from 6 days ago (Jan 26th, 2017) f40814710e2bd38c26366fb6ec3c3aba0c882406 I was able to get a koha container running and connected to an external mysql container. The automated webinstaller seemed to run fine when I tail the koha container logs, and both OPAC and Intra respond on 8080 and 8081.

Now I need to login, but admin / secret isn't working - simply says I've entered an incorrect username or password.

What are the default creds when using the docker image?

Thanks! Great project, looking forward to deploying to production!

PS. The more recent docker hub tags from 2 days ago weren't working. I tried several, but none could connect to mysql despite using the same -e docker args that worked for the latest tag from 6 days ago.

How to set up a container with your dockerfile not clear for a beginner

Hi,

I'm quite new with docker, so I guess the problem is more of a comprehension problem than a real bug. So I'm trying to set up a docker container based on your work, unfortunately, that didn't work well for me. I'm trying to understand what the « [tag/revision] » mean in « digibib/koha:[tag/revision] »! I know, it must seem obvious for you, but for me, it's quite obscure;

• I can't see any tag on your git repository;
• I've tried the docker command (docker run --interactive --name koha_docker -p 6001:6001 -p 8080:8080 -p 8081:8081 -t) with the following tags:
  • « digibib/koha:3.22.01 »
  • « digibib/koha:[3.22.01] »
  • « digibib/koha:98eef6f »
  • « digibib/koha:[98eef6f] »

Can you tell me what is the exact syntax?

Thanks in advance!

Emmanuel Di Pretoro

Project wiki inaccessible

When clicking on the link to the project wiki (https://gitlab.deichman.no/digibib/koha-docker/wiki) access is denied (I am guessing for most people).

It would be great if the content could still be accessed..!

How do we manage security updates?

(Question from theodotos – found here: https://registry.hub.docker.com/u/digibib/koha/ )

Your koha-conf.xml does not contain a valid upload_path.

I'm trying to enable file uploads as shown in http://bywatersolutions.com/2017/06/08/attach-file-marc-records/, which works fine. But when uploading a file, I get

Your koha-conf.xml does not contain a valid upload_path.

Aparently, this is true as https://github.com/digibib/koha-docker/blob/master/files/templates/instance/koha-conf.xml.tmpl just contains

<upload_path></upload_path>

Is there a nice way to set the upload_path through docker-compose and point the upload path to a docker-compose volume? For example, can I set the upload path through an environment variable?

Thanks!

deichman.no repositories are broken

I'm trying to build project with make passes a few steps but deichman.no links breaks build session. The error messages generated by make is below :

W: Failed to fetch http://datatest.deichman.no/repositories/koha/public/dists/wheezy/InRelease

W: Failed to fetch http://datatest.deichman.no/repositories/koha/public/dists/wheezy/Release.gpg Unable to connect to datatest.deichman.no:http:

W: Some index files failed to download. They have been ignored, or old ones used instead.

Can't start up with docker-compose

Hi there.

First of all many thanks for your time.

Since it's my first interaction with docker koha maybe I didn't follow the right steps.

Steps to reproduce:

1. Clone repo:

git clone https://gitlab.deichman.no/digibib/koha

2. Clone repo

git clone https://gitlab.deichman.no/digibib/koha-docker

3. Try to bring up a development environment with docker-compose:

cd koha-docker/docker-compose
source docker-compose.env && KOHAPATH=.. docker-compose -f common.yml -f dev.yml build koha_dev

Expected behaviour:

See the docker-compose logs indicating that all containers are started up

Found behaviour:

Below error:

...
Step 16/33 : ENV QATOOLS_REPO https://github.com/Koha-Community/qa-test-tools.git
 ---> Running in 9b8d58f8f0d3
Removing intermediate container 9b8d58f8f0d3
 ---> a3f2eff22cf7
Step 17/33 : RUN DEBIAN_FRONTEND=noninteractive apt-get update &&     sudo apt-get install -q -y cpanminus vim net-tools git-email telnet screen wget less curl htop &&     apt-get clean
 ---> Running in 620e1be14370
Ign http://static.deichman.no wheezy InRelease
Get:1 http://debian.koha-community.org unstable InRelease [4568 B]
Get:2 http://debian.koha-community.org stable InRelease [4565 B]
Get:3 http://security.debian.org jessie/updates InRelease [44.9 kB]
Ign http://static.deichman.no wheezy Release.gpg
Ign http://deb.debian.org jessie InRelease
Get:4 http://static.deichman.no wheezy Release [2694 B]
Get:5 http://deb.debian.org jessie-updates InRelease [7340 B]
Get:6 http://static.deichman.no wheezy/main amd64 Packages [190 kB]
Hit http://deb.debian.org jessie Release.gpg
Hit http://deb.debian.org jessie Release
Get:7 http://debian.koha-community.org unstable/main amd64 Packages [20.8 kB]
Get:8 http://debian.koha-community.org stable/main amd64 Packages [19.1 kB]
Get:9 http://security.debian.org jessie/updates/main amd64 Packages [825 kB]
Get:10 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Fetched 10.2 MB in 42s (238 kB/s)
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.
ERROR: Service 'koha_dev' failed to build: The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive apt-get update &&     sudo apt-get install -q -y cpanminus vim net-tools git-email telnet screen wget less curl htop &&     apt-get clean' returned a non-zero code: 100

Container Crashes on Restart of Server

First off, love how easy you made it to be able to start up a local Koha instance. I pull it up with ease when I originally create the container and everything works great until I restart the system and then there's a crash that happens consistently when starting the mysql db server. Log attached here:
koha-log.pdf

Any ideas how to get this working when the system restarts?

Koha requires mpm_itk

Got this error fromfd88134:

koha          | Koha requires mpm_itk to be enabled within Apache in order to run.
koha          | Typically this can be enabled with:
koha          |
koha          |     sudo a2enmod mpm_itk
koha          |
koha exited with code 1

Rolled back to fe360b6 (last commit 16 days ago) and the error disappeared. Didn't try the commits in-between. Have you run into this?

Cannot login

Hi, I'm hoping to experiment with Koha for the first time, so I'm trying to start up Koha on docker for the first time.

I've cloned the most recent koha-docker (6f9f535) and digibib/koha (f04cd87) repos but I cannot login to localhost:8081 with admin/secret. I get the error "Error: Invalid username or password".

Looking at /var/log/mysql/error.log, there is an error:

ERROR: 1064  You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for
 the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
180822 11:49:44 [ERROR] Aborting
180822 11:49:44  InnoDB: Starting shutdown...

so presumably mysql isn't running. I've searched through the source (both repos) for show_view_priv but can't find it mentioned. Is this a red herring? mysql should actually be running in a different container shouldn't it?

Can't save records to new install. "DCHM" framework not found.

Hi,

After getting the build scripts working, things were looking good but my users receive "internal server error" when trying to save any records.

The logs mention No biblionumber tag for framework "DCHM" at /usr/share/koha/lib/C4/Biblio.pm line 3093 which appears to be related to some patches in koha-docker - at least, that's the only reference to "DCHM" I could find.

Any ideas?

You've mentioned running these docker images in production, so I'm keen to get there too.

Thanks again for the help!

Should this be used in production?

Should this repo be used in production or is this purely for developing purposes? How do you do upgrades and database migrations?

kohadcos typographical error

When trying to get a kohadevbox to run on Ubuntu, difficulties ensured, but one was due to vars/defaults.yml (and not really vars/user.yml.sample) having kohadcos instead of kohadocs in the file. This triggered an error about "mkdir -p ''" when trying to provision it for the first time.