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
The user_guide.md give the following example for loading a custom specification file in the chapter Using Custom VSS Data Entries.
docker run --rm -it -p 55555:55555 ghcr.io/eclipse-kuksa/kuksa-databroker:main --insecure --vss vss.json
See: https://github.com/eclipse-kuksa/kuksa-databroker/blob/main/doc/user_guide.md#using-custom-vss-data-entries
This results in the following error message:
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
The solution would be to map the file into the docker container.
docker run --rm -it -p 55555:55555 -v ./vss.json:/vss.json ghcr.io/eclipse-kuksa/kuksa-databroker:main --insecure --vss vss.json
Maybe this should be added to the documentation.
The text was updated successfully, but these errors were encountered:
If you would be so kind and create a PR for this we would appreciate it :)
Sorry, something went wrong.
No branches or pull requests
The user_guide.md give the following example for loading a custom specification file in the chapter Using Custom VSS Data Entries.
docker run --rm -it -p 55555:55555 ghcr.io/eclipse-kuksa/kuksa-databroker:main --insecure --vss vss.json
See: https://github.com/eclipse-kuksa/kuksa-databroker/blob/main/doc/user_guide.md#using-custom-vss-data-entries
This results in the following error message:
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
The solution would be to map the file into the docker container.
docker run --rm -it -p 55555:55555 -v ./vss.json:/vss.json ghcr.io/eclipse-kuksa/kuksa-databroker:main --insecure --vss vss.json
Maybe this should be added to the documentation.
The text was updated successfully, but these errors were encountered: