This HTML5 document contains 30 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n22http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep5#
n21http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep18#
n28http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep16#
n20http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep14#
n13http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep10#
n18http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep4#
n19https://www.openlinksw.com/about/id/entity/http/www.openlinksw.com/data/turtle/general/
n16http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep12#
n27http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep3#
wdrshttp://www.w3.org/2007/05/powder-s#
oplsofthttp://www.openlinksw.com/ontology/software#
n15http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep2#
n2http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImage#
schemahttp://schema.org/
n24https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n12https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n8http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep1#
n17http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep9#
n14http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep15#
n25https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n6http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep19#
n10http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep13#
n5http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep17#
n7http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep11#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n26http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep8#
n9http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep7#
xsdhhttp://www.w3.org/2001/XMLSchema#
n23http://data.openlinksw.com/oplweb/howto/HowDoIInstallVirtuosoDockerContainerImageStep6#

Statements

Subject Item
n2:this
wdrs:describedby
n12:virtuoso-howto-install-guides.ttl n19:virtuoso-howto-install-guides.ttl n24:websites n25:virtuoso-howto-install-guides.ttl
schema:name
How Do I Install Virtuoso Docker Container Image?
oplsoft:hasDatabaseFamily
http://data.openlinksw.com/oplweb/dbms_family/OpenLinkVirtuoso#this
oplsoft:hasOperatingSystemFamily
http://data.openlinksw.com/oplweb/opsys_family/GenericLinux
schema:category
Installation Guide
schema:text
<ol> <li><strong>Choose Docker Image:</strong> <ul> <li>We’ve put together three Docker Images to choose from (<a href="https://hub.docker.com/u/openlink/">https://hub.docker.com/u/openlink/</a>). The Enterprise Edition images require a version-matched license file, while the Open Source (“VOS”) image does not. <ul> <li>Enterprise Edition 8.3 – <a href="https://hub.docker.com/r/openlink/virtuoso-closedsource-8/">openlink/virtuoso-closedsource-8</a></li> <li>Enterprise Edition 7.2 – <a href="https://hub.docker.com/r/openlink/virtuoso-closedsource-7/">openlink/virtuoso-closedsource-7</a></li> <li>Open Source (“VOS”) 7.2 – <a href="https://hub.docker.com/r/openlink/virtuoso-opensource-7/">openlink/virtuoso-opensource-7</a></li> </ul> </li> </ul> <blockquote>The remainder of this article focuses on Enterprise Edition 8.3; most content applies to all three, with minor adjustments.</blockquote> </li> <li><strong>Download Docker Image:</strong> <ul> <li>To pull the latest Virtuoso 8.2 docker 8 image to your local system, use the command: <pre>$ docker pull openlink/virtuoso-closedsource-8</pre> </li> <li>To check the version of the Virtuoso binary, use the command: <pre>$ docker run openlink/virtuoso-closedsource-8 version</pre> <samp>This Docker image is using Virtuoso Universal Server (Enterprise Edition) Version 08.03.3319-pthreads as of Sep 9 2020, compiled for Linux (x86_64-generic-linux-glibc25).</samp> </li> </ul> </li> <li><strong>Creating a Sample Virtuoso Docker Instance:</strong> <ul> <li>Create a new virtuoso instance on your system with the following commands: <pre>$ mkdir my_virtdb $ cd my_virtdb $ docker run \ --name my_virtdb \ --interactive \ --tty \ --env DBA_PASSWORD=mysecret \ --publish 1111:1111 \ --publish 8890:8890 \ --volume `pwd`:/database \ openlink/virtuoso-closedsource-8:latest</pre> <li>This creates a new Virtuoso database in the my_virtdb subdirectory and starts a Virtuoso instance with the HTTP server listening on port 8890 and the ODBC / JDBC / ADO.Net / OLE-DB / ISQL data server listening on port 1111.</li> <li>The docker image runs in foreground mode, allowing you to see its activity.</li> <li>Access the Virtuoso HTTP server at <a href="http://localhost:8890/">http://localhost:8890/</a>.</li> <li>Shut down Virtuoso by pressing CTRL and C in the terminal session.</li> </li> </ul> </li> <li><strong>Licensing:</strong> <ul> <li>If the Virtuoso Enterprise Edition binary cannot find a license, it will start with a restrictive courtesy license which allows limited concurrent connections and terminates the instance after 10 minutes of use.</li> <li>Obtain a FREE Evaluation License via our License Generator Web Service (<a href="https://shop.openlinksw.com/license_generator/virtuoso/">https://shop.openlinksw.com/license_generator/virtuoso/</a>).</li> <li>Place the resulting virtuoso.lic file in the newly created database/ directory alongside the virtuoso.ini on your local filesystem for the docker image to pick up on the next startup: <pre>$ docker cp virtuoso.lic my_virtdb:/database $ docker stop my_virtdb $ docker start my_virtdb</pre> </li> </ul> </li> <li><strong>Passwords:</strong> <ul> <li>When a new database is created, the docker image will use the Environment settings DBA_PASSWORD and DAV_PASSWORD to set passwords for the dba and dav user accounts.</li> <li>If the DBA_PASSWORD environment variable is not set, a random password will be assigned to the dba user account, stored on the internal docker filesystem as /settings/dba_password.</li> <li>If the DAV_PASSWORD environment variable is not set, it will be set to the DBA_PASSWORD and stored as /settings/dav_password.</li> <li>These files will only be readable by the user who started the image. Use the following command to reveal the randomized passwords: <pre>$ docker exec -i -t my_virtdb cat /settings/dba_password</pre> </li> <li><strong>NOTE:</strong> Users are advised to immediately change the password and then remove this file from the filesystem.</li> </ul> </li> <li><strong>Persistent Storage:</strong> <ul> <li>To retain changes to the Virtuoso database, the database documents should be stored on the host file system.</li> <li>The docker image exposes a /database volume that can be mapped to a local directory on the filesystem. If this directory is empty, the docker image will put an initial virtuoso.ini into the mapped directory and then create a new database.</li> </ul> </li> <li><strong>Stopping the Image:</strong> <ul> <li>When the docker image is running in foreground mode, shut down Virtuoso by pressing the CTRL and C buttons in that terminal session. Alternatively, use the following command in a different terminal: <pre>$ docker stop my_virtdb</pre> </li> </ul> </li> <li><strong>Restarting the Image:</strong> <ul> <li>Once the docker image has been registered with the docker run or docker create command on your local system, start it in the background using: <pre>$ docker start my_virtdb</pre> </li> <li>For foreground mode, use: <pre>$ docker start -i -a my_virtdb</pre> </li> </ul> </li> <li><strong>Checking the Startup Log:</strong> <ul> <li>If the docker image is started in background mode, look at the recent output of the virtuoso process by running: <pre>$ docker logs my_virtdb</pre> </li> </ul> </li> <li><strong>Using isql to Connect:</strong> <ul> <li>To connect to your running Virtuoso 11 instance, use the following command: <pre>$ docker exec -i my_virtdb isql 1111</pre> <li>You will be prompted for the dba account password.</li> <li><strong>NOTE:</strong> Multiple incorrect password attempts will lock the dba account for a couple of minutes.</li> </li> </ul> </li> <li><strong>Using an Existing Database:</strong> <ul> <li>If the mapped directory contains a virtuoso.ini and accompanying database documents, the new docker image will attempt to use these.</li> <li><strong>NOTE:</strong> Directory paths in the virtuoso.ini should be relative to the internal directory structure of the docker image to function correctly.</li> </ul> </li> </ol> <ol> <li><strong>Choose Docker Image:</strong> <ul> <li>We’ve put together three Docker Images to choose from (<a href="https://hub.docker.com/u/openlink/">https://hub.docker.com/u/openlink/</a>). The Enterprise Edition images require a version-matched license file, while the Open Source (“VOS”) image does not. <ul> <li>Enterprise Edition 8.3 – <a href="https://hub.docker.com/r/openlink/virtuoso-closedsource-8/">openlink/virtuoso-closedsource-8</a></li> <li>Enterprise Edition 7.2 – <a href="https://hub.docker.com/r/openlink/virtuoso-closedsource-7/">openlink/virtuoso-closedsource-7</a></li> <li>Open Source (“VOS”) 7.2 – <a href="https://hub.docker.com/r/openlink/virtuoso-opensource-7/">openlink/virtuoso-opensource-7</a></li> </ul> </li> </ul> <blockquote>The remainder of this article focuses on Enterprise Edition 8.3; most content applies to all three, with minor adjustments.</blockquote> </li> <li><strong>Download Docker Image:</strong> <ul> <li>To pull the latest Virtuoso 8.2 docker image to your local system, use the command: <pre>$ docker pull openlink/virtuoso-closedsource-8</pre> </li> <li>To check the version of the Virtuoso binary, use the command: <pre>$ docker run openlink/virtuoso-closedsource-8 version</pre> <samp>This Docker image is using Virtuoso Universal Server (Enterprise Edition) Version 08.03.3319-pthreads as of Sep 9 2020, compiled for Linux (x86_64-generic-linux-glibc25).</samp> </li> </ul> </li> <li><strong>Creating a Sample Virtuoso Docker Instance:</strong> <ul> <li>Create a new virtuoso instance on your system with the following commands: <pre>$ mkdir my_virtdb $ cd my_virtdb $ docker run \ --name my_virtdb \ --interactive \ --tty \ --env DBA_PASSWORD=mysecret \ --publish 1111:1111 \ --publish 8890:8890 \ --volume `pwd`:/database \ openlink/virtuoso-closedsource-8:latest</pre> <li>This creates a new Virtuoso database in the my_virtdb subdirectory and starts a Virtuoso instance with the HTTP server listening on port 8890 and the ODBC / JDBC / ADO.Net / OLE-DB / ISQL data server listening on port 1111.</li> <li>The docker image runs in foreground mode, allowing you to see its activity.</li> <li>Access the Virtuoso HTTP server at <a href="http://localhost:8890/">http://localhost:8890/</a>.</li> <li>Shut down Virtuoso by pressing CTRL and C in the terminal session.</li> </li> </ul> </li> <li><strong>Licensing:</strong> <ul> <li>If the Virtuoso Enterprise Edition binary cannot find a license, it will start with a restrictive courtesy license which allows limited concurrent connections and terminates the instance after 10 minutes of use.</li> <li>Obtain a FREE Evaluation License via our License Generator Web Service (<a href="https://shop.openlinksw.com/license_generator/virtuoso/">https://shop.openlinksw.com/license_generator/virtuoso/</a>).</li> <li>Place the resulting virtuoso.lic file in the newly created database/ directory alongside the virtuoso.ini on your local filesystem for the docker image to pick up on the next startup: <pre>$ docker cp virtuoso.lic my_virtdb:/database $ docker stop my_virtdb $ docker start my_virtdb</pre> </li> </ul> </li> <li><strong>Passwords:</strong> <ul> <li>When a new database is created, the docker image will use the Environment settings DBA_PASSWORD and DAV_PASSWORD to set passwords for the dba and dav user accounts.</li> <li>If the DBA_PASSWORD environment variable is not set, a random password will be assigned to the dba user account, stored on the internal docker filesystem as /settings/dba_password.</li> <li>If the DAV_PASSWORD environment variable is not set, it will be set to the DBA_PASSWORD and stored as /settings/dav_password.</li> <li>These files will only be readable by the user who started the image. Use the following command to reveal the randomized passwords: <pre>$ docker exec -i -t my_virtdb cat /settings/dba_password</pre> </li> <li><strong>NOTE:</strong> Users are advised to immediately change the password and then remove this file from the filesystem.</li> </ul> </li> <li><strong>Persistent Storage:</strong> <ul> <li>To retain changes to the Virtuoso database, the database documents should be stored on the host file system.</li> <li>The docker image exposes a /database volume that can be mapped to a local directory on the filesystem. If this directory is empty, the docker image will put an initial virtuoso.ini into the mapped directory and then create a new database.</li> </ul> </li> <li><strong>Stopping the Image:</strong> <ul> <li>When the docker image is running in foreground mode, shut down Virtuoso by pressing the CTRL and C buttons in that terminal session. Alternatively, use the following command in a different terminal: <pre>$ docker stop my_virtdb</pre> </li> </ul> </li> <li><strong>Restarting the Image:</strong> <ul> <li>Once the docker image has been registered with the docker run or docker create command on your local system, start it in the background using: <pre>$ docker start my_virtdb</pre> </li> <li>For foreground mode, use: <pre>$ docker start -i -a my_virtdb</pre> </li> </ul> </li> <li><strong>Checking the Startup Log:</strong> <ul> <li>If the docker image is started in background mode, look at the recent output of the virtuoso process by running: <pre>$ docker logs my_virtdb</pre> </li> </ul> </li> <li><strong>Using isql to Connect:</strong> <ul> <li>To connect to your running Virtuoso instance, use the following command: <pre>$ docker exec -i my_virtdb isql 1111</pre> <li>You will be prompted for the dba account password.</li> <li><strong>NOTE:</strong> Multiple incorrect password attempts will lock the dba account for a couple of minutes.</li> </li> </ul> </li> <li><strong>Using an Existing Database:</strong> <ul> <li>If the mapped directory contains a virtuoso.ini and accompanying database documents, the new docker image will attempt to use these.</li> <li><strong>NOTE:</strong> Directory paths in the virtuoso.ini should be relative to the internal directory structure of the docker image to function correctly.</li> </ul> </li> </ol>
rdf:type
schema:HowTo
schema:step
n5:this n6:this n7:this n8:this n9:this n10:this n13:this n14:this n15:this n16:this n17:this n18:this n20:this n21:this n22:this n23:this n26:this n27:this n28:this