Description of the Problem
The Jetleg project uses Docker to build container images that preserve a snapshot of computing environment that can be used to run software in the same environment as was used during the software's development. The project uses Docker images for two main reasons. First, the images easily allow the software to be deployed on the Jetson Nano which uses a different computer architecture from most conventional computers. Second, we use development images to easily provide members with a current development environment to avoid the lengthy process of installing dependencies. The current configuration Docker for this project was implemented in an ad hoc manner, so there exist areas for improvement such as using Docker volumes to avoid rebuilding an image after a slight change in the software's source code, using Docker networks to allow multiple instances of the software to run on the same machine for testing purposes for example, or using arguments and environment variables to make a single image more versatile. This issue focuses on simply reviewing the current configuration, identifying further issues, and proposing a solution for the identified issues.
Suggested Actions
Description of the Problem
The Jetleg project uses Docker to build container images that preserve a snapshot of computing environment that can be used to run software in the same environment as was used during the software's development. The project uses Docker images for two main reasons. First, the images easily allow the software to be deployed on the Jetson Nano which uses a different computer architecture from most conventional computers. Second, we use development images to easily provide members with a current development environment to avoid the lengthy process of installing dependencies. The current configuration Docker for this project was implemented in an ad hoc manner, so there exist areas for improvement such as using Docker volumes to avoid rebuilding an image after a slight change in the software's source code, using Docker networks to allow multiple instances of the software to run on the same machine for testing purposes for example, or using arguments and environment variables to make a single image more versatile. This issue focuses on simply reviewing the current configuration, identifying further issues, and proposing a solution for the identified issues.
Suggested Actions