Docker-BBQ
Creating flexible docker images with the ability quickly and efficiently develop and execute code can be time consuming. There are generally two competing goals, keeping images small for deployment, while making them usable during development. On top of that, there are a number of special flags and features of docker that can be forgotten when starting a new project. This project aims to codify a standard approach to creating and running docker based projects.
The user can select between a number of bundled templates, which at the time of writing are limited to:
- Ubuntu
- Debian
- ROS
- Alpine
Using docker-bbq, the user can simply execute bbq-create Alpine my-test-project to get generate a new project.
That project comes with a Makefile that takes care of building the images.
There are two different build types: development, which is the default, and production, which is used for deployment.
In the development image, the user’s code is mounted into the image at run-time.
This means that the user doesn’t need to rebuild the image every time they make a change.
Docker-bbq also provides a run command that manages running, mounting the workspace, translating execution paths during development.
Using the run command, the user can seamlessly execute things in the image as if they were executing in the host machine.
The production image on the other hand is compiled with the workspace inside the image.
It is not designed to be used during development, which means the run command is not available for this image.
The user needs to execute the image using plain Docker commands, which is how it would be used in production.
My local development environment for this website is a bbq-docker project.
Demonstration
This clip is a little out-of-date, but it shows the general idea of the project.