| Table of Contents | ||
|---|---|---|
|
...
| Note |
|---|
When running the pull command, please note that if an image is already running and you pull the latest one, it will overwrite existing data in the knowledge graph repository, resetting it to the default state. To avoid losing your data, follow the guidelines on the provided /wiki/spaces/ENAPSODOCS/pages/2239528974 to create a backup before pulling the latest image, and then restore your data afterward. |
...
| Code Block | ||
|---|---|---|
| ||
docker pull registry.innotrade.com/innotrade/enapso-together-free |
...
This maps the container's port 80 to your local machine's port 80.
Resolving Port Conflicts
If you encounter a port conflict when attempting to run the Docker container for the ENAPSO together Free platform, you have an the following option to resolve it and access the service:.
Change the Host Port
If port 80 is already in use on your machine, you can map the container's internal port (80) to a different port on your host. For example, if you choose to use port 8080 on your host, you can modify your Docker run command like this:
...
Run Docker Container with Triplestore UI Access
To run the ENAPSO Together Free together free platform and enable access to the triplestore UI for enhanced monitoring and management, use the following Docker command:
...
| Note |
|---|
When running the pull command, please note that if an image is already running and you pull the latest one, it will overwrite existing data in the knowledge graph repository, resetting it to the default state. To avoid losing your data, follow the guidelines on the provided /wiki/spaces/ENAPSODOCS/pages/2239528974 to create a backup before pulling the latest image, and then restore your data afterward. |
...
Upload Demo Data via enapso-graphdb-cli tool
...