Issues in Docker Image and Generation Scripts #1004
Assignees
Labels
bug
Scope: Documentation
This issue relates to OSCAL documentation.
Scope: Website
Issues targeted at the OSCAL project website.
Milestone
Comments
stephenbanghart
added
bug
Scope: Website
david-waltermire
added a commit
to david-waltermire/OSCAL
that referenced
this issue
Aug 5, 2021
Also made docs Docker container dependent on the build container, which should ease future maintenance. Updated readmes to address docker 20.10 compose syntax, and to add new dependencies. Changed location of profile-resolution.html. Resolves usnistgov#1004.
8 tasks
david-waltermire
added a commit
that referenced
this issue
Aug 5, 2021
Also made docs Docker container dependent on the build container, which should ease future maintenance. Updated readmes to address docker 20.10 compose syntax, and to add new dependencies. Changed location of profile-resolution.html. Resolves #1004.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The Docker Image as provided fails when running build/ci-cd/generate-model-documentation.sh, preventing the image from building website. The specific error is
Error: Could not find or load main class com.xmlcalabash.drivers.Main. This error triggers on most of the child scripts.The generate-specification-documentation.sh script has not been updated to reflect the new file structure of /docs, and creates a new /docs/content/documentation/processing/ folder. It should instead place the generated HTML in /docs/content/concepts/processing.
Docker has integrated compose into the default docker CLI, support is waning for docker-compose, I suggest the READMEs and Image make the switch over. See: Discussion around continued support of docker-compose
docker-compose {args} -> docker compose {args}
Who is the bug affecting?
Users of the docker image. Users of the generate-specification-documentation.sh script.
The text was updated successfully, but these errors were encountered: