You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Docker build fails without a manual step related to certificates that is neither automated or documented in the build instructions as far as I can see. Depending on how it should be handled it appears to be a documentation and or build automation error.
I could also not find documentation for this step in the tutorial or build instructions in the root README so its possible that this also applies to the general non-docker case for newcomers to the project.
Notes
As Renjith mentions a path to a solution is documented in the testCredGen readme, but this is only arrived at by debugging the failure and trying to figure out what is needed to fill the gap, rather than a description of the runtime environment for the server in its setup documentation. At the time of writing its unknown if the testCredGen README has sufficient information to solve the issue.
As an aside this issue would need to be addressed if the project wished to push a WAII image to a Docker image repository.
See #87 for manual workaround: create sub-directory and manually run script
In my case I am consuming WAII in the downstream Covesa project Central Data Service Playground. One goal of the playground is very simple accessibility (ease of setup) so we are interested in finding and fixing these gaps with you.
The text was updated successfully, but these errors were encountered:
slawr
changed the title
Docker instructions insufficient for succesful deployment - believe this applies to non-docker as well
Docker instructions insufficient for succesful deployment - believe this applies to non-docker as well. Missing Certificate Authority
Dec 8, 2023
PR #90 does appear to address issue #87, i.e. the directory no longer needs to be manually created and the script successfully generates the certs. This was confirmed today during a joint debug session where I was trying to help Arnaldo through WAII build issues on a clean Central Data Service Playground build.
This joint session however confirmed that whilst the script now succeeds the Docker build still fails as the dockerfile only copies the generated certs but does not run the script. That requirement is not mitigated by any build setup instruction in the Docker doc. A developer must figure it out through debugging the build failure.
In the non-Docker case there is nothing I could find in the build instructions in
or https://w3c.github.io/automotive-viss2/build-system/ that is required. If it isn't required for a standard build of the non-Docker source then of course that is fine, but I mention it here in case it also needs to be addressed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
Re-opening the build issue previously raised by Renjith @volvorenjithraj #58
Failure occurs at
automotive-viss2/Dockerfile
Line 37 in 852b779
Docker build fails without a manual step related to certificates that is neither automated or documented in the build instructions as far as I can see. Depending on how it should be handled it appears to be a documentation and or build automation error.
I could also not find documentation for this step in the tutorial or build instructions in the root README so its possible that this also applies to the general non-docker case for newcomers to the project.
Notes
As Renjith mentions a path to a solution is documented in the testCredGen readme, but this is only arrived at by debugging the failure and trying to figure out what is needed to fill the gap, rather than a description of the runtime environment for the server in its setup documentation. At the time of writing its unknown if the testCredGen README has sufficient information to solve the issue.
As an aside this issue would need to be addressed if the project wished to push a WAII image to a Docker image repository.
See #87 for manual workaround: create sub-directory and manually run script
In my case I am consuming WAII in the downstream Covesa project Central Data Service Playground. One goal of the playground is very simple accessibility (ease of setup) so we are interested in finding and fixing these gaps with you.
The text was updated successfully, but these errors were encountered: