Page 1 of 1

Actual docker version creates unexpected volume

PostPosted:Tue Oct 13, 2020 10:15 am
by HugoHiasl
Hi,

I did set up the docker version on a linux server and it works like a charm with my postgres also running in a docker container.

For the repository I did mount a volume on the host system to make backups and upgrades easier.

When I take a look on portainer on the running openkm-ce container I see an additional volume that I did not mount there. Is this needed? What is the intention about it?

Thanks a lot.
2020-10-13 12_11_05-Portainer.png
2020-10-13 12_11_05-Portainer.png (32.09 KiB) Viewed 3409 times

Re: Actual docker version creates unexpected volume

PostPosted:Thu Oct 15, 2020 9:22 am
by pavila
Which volume are you talking about?

Re: Actual docker version creates unexpected volume

PostPosted:Fri Oct 16, 2020 7:15 pm
by HugoHiasl
The one that is mounted to /opt/tomcat with the internal generated name.

In the image the second last row.

I ran it with

docker run .... -v /data/docker volumes/openkm_data:/opt/tomcat/repository

no additional second -v for the docker data volume.

Re: Actual docker version creates unexpected volume

PostPosted:Mon Nov 02, 2020 12:44 pm
by pavila
Please, take a look at https://docs.openkm.com/kcenter/view/ok ... ocker.html

According to the Dockerfile the only volume should be "/opt/tomcat", or at least , it's the default one. In the documentation some other files or directories are mounted as volumes to make possible changing the default configuration:

- ${PWD}/server.xml:/opt/tomcat/conf/server.xml
- ${PWD}/OpenKM.cfg:/opt/tomcat/OpenKM.cfg
- ${PWD}/repository:/opt/tomcat/repository

So, depending on you want the default configuration or use another database you can use different volumes. I don't recomment using the default configuration for production because it will use an embedded database.