DockerFile Findings for Follow Up Efforts - DevOps-MBSE/AaC GitHub Wiki

Some research was done regarding the possibility of having a central Docker file in the .github repository. Other AaC repositories would access that central Docker file for their own docker container needs, potentially with specific repository additions. While this seems feasible, cross repository docker file usage was determined to not be straightforward.

My initial reading of some sites suggested that this could be a possibility https://stackoverflow.com/questions/69234878/using-shared-dockerfile-for-multiple-dockerfiles. Upon re-reading, however, most of the documentation and discussions on this topic are oriented to multiple Docker files within a single repository.

  1. AaC
  2. aac-gherkin
  3. aac-rest-api
  4. aac-spec

Additionally, the aac-puml repository was aligned to the source Docker file but also has an additional install specific to that repository. This is an example of extended the base source file.

Currently: With the current implementation it is now up to the AaC team to keep these files aligned.

Future Work: Additional research, or discussion with someone more experienced with containers across multiple github repositories, may reveal a solution to having a single file, with potential extensions specific to each repository as needed. This would be a more ideal solution.