We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I didn't found setup/init scripts to do this on start. how does iptables called?
`> $ COLLECTION_URI=https://databus.dbpedia.org/dbpedia/collections/latest-core VIRTUOSO_ADMIN_PASSWD=password docker-compose up [±master ●] Pulling store (openlink/virtuoso-opensource-7:7.2)... 7.2: Pulling from openlink/virtuoso-opensource-7 Digest: sha256:a6c0d9200a2932777fdc4695b1c46a36e3be58708602260ec5f65da560001e9f Status: Downloaded newer image for openlink/virtuoso-opensource-7:7.2 Creating virtuoso-sparql-endpoint-quickstart_download_1 ... Creating virtuoso-sparql-endpoint-quickstart_load_1 ... Creating virtuoso-sparql-endpoint-quickstart_store_1 ... Creating virtuoso-sparql-endpoint-quickstart_store_1 ... error
ERROR: for virtuoso-sparql-endpoint-quickstart_store_1 Cannot start service store: driver failed programming external connectivity on endpoint virtuoso-sparql-endpoint-quickstart_store_1 (f3aaff54808709a4833922f5844c636a2daa94b7cd10721b323a5eb1e3cccef6): (iptables failedCreating virtuoso-sparql-endpoint-quickstart_download_1 ... done Creating virtuoso-sparql-endpoint-quickstart_load_1 ... done (exit status 2))
ERROR: for store Cannot start service store: driver failed programming external connectivity on endpoint virtuoso-sparql-endpoint-quickstart_store_1 (f3aaff54808709a4833922f5844c636a2daa94b7cd10721b323a5eb1e3cccef6): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 8898 -j DNAT --to-destination 172.18.0.4:8890 ! -i br-c9ca5b93c64b: iptables v1.8.7 (legacy): unknown option "--to-destination" Try iptables -h' or 'iptables --help' for more information. (exit status 2)) ERROR: Encountered errors while bringing up the project.
iptables -h' or 'iptables --help' for more information. (exit status 2)) ERROR: Encountered errors while bringing up the project.
how could i fix this? thanks.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I didn't found setup/init scripts to do this on start. how does iptables called?
`> $ COLLECTION_URI=https://databus.dbpedia.org/dbpedia/collections/latest-core VIRTUOSO_ADMIN_PASSWD=password docker-compose up [±master ●]
Pulling store (openlink/virtuoso-opensource-7:7.2)...
7.2: Pulling from openlink/virtuoso-opensource-7
Digest: sha256:a6c0d9200a2932777fdc4695b1c46a36e3be58708602260ec5f65da560001e9f
Status: Downloaded newer image for openlink/virtuoso-opensource-7:7.2
Creating virtuoso-sparql-endpoint-quickstart_download_1 ...
Creating virtuoso-sparql-endpoint-quickstart_load_1 ...
Creating virtuoso-sparql-endpoint-quickstart_store_1 ...
Creating virtuoso-sparql-endpoint-quickstart_store_1 ... error
ERROR: for virtuoso-sparql-endpoint-quickstart_store_1 Cannot start service store: driver failed programming external connectivity on endpoint virtuoso-sparql-endpoint-quickstart_store_1 (f3aaff54808709a4833922f5844c636a2daa94b7cd10721b323a5eb1e3cccef6): (iptables failedCreating virtuoso-sparql-endpoint-quickstart_download_1 ... done
Creating virtuoso-sparql-endpoint-quickstart_load_1 ... done
(exit status 2))
ERROR: for store Cannot start service store: driver failed programming external connectivity on endpoint virtuoso-sparql-endpoint-quickstart_store_1 (f3aaff54808709a4833922f5844c636a2daa94b7cd10721b323a5eb1e3cccef6): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 8898 -j DNAT --to-destination 172.18.0.4:8890 ! -i br-c9ca5b93c64b: iptables v1.8.7 (legacy): unknown option "--to-destination"
Try
iptables -h' or 'iptables --help' for more information. (exit status 2)) ERROR: Encountered errors while bringing up the project.
how could i fix this? thanks.
The text was updated successfully, but these errors were encountered: