Closed mjovanovik closed 7 years ago
I managed to solve the issue. The platform was placed on a mounted file system, so docker
needed a privileged status for gaining access to the config/db
directory.
The solution is to add the --privileged=true
flag in a docker run
command, or in the case of the platform, to add a new privileged: true
line in docker-compose.yml
for the service in question:
# Triple store
virtuoso:
privileged: true
image: openlink/virtuoso_opensource:vos
container_name: vos
hostname: vos
volumes:
- ./config/db:/opt/virtuoso-opensource/var/lib/virtuoso/db
networks:
- hobbit-core
ports:
- "8890:8890"
If this solves your problem too, you will need to add the privileged: true
setting for all services in docker-compose.yml
which use a volume: platform-controller
, keycloak
and virtuoso
.
I'm trying to start Virtuoso as part of the platform, using
docker-compose up virtuoso
. Whenever I try this, Virtuoso keeps shutting down immediately, with a report stating that it is missing thevirtuoso.ini
file.Apparently, the mount of the
config/db
directory is not successful, as it contains the necessaryvirtuoso.ini
file.I'm using CentOS 7.3, the file system is
xfs
, whiledocker
anddocker-compose
haveroot
permissions.