Add dev convenience script for building containers

[asavageiv]

A small script to make building the containers for local dev testing a little easier:

Usage: ./scripts/build-containers.sh [--variant develop|beta] <container1> [container2] [container3] ...
Example: ./scripts/build-containers.sh --variant beta apache mastercontainer

Feel free to reject this if there's a better way.

[szaimen]

Hi I am not sure about adding this to the repo as we would also need to maintain it then. Wdyt @pabzm?

[pabzm]

I don't need this script, but also wouldn't mind it – but I'd also prefer to only include such scripts if multiple devs or contributors would like to use it.

[asavageiv]

Out of curiousity, how do you all build the containers when doing local dev? Do you just type it out every time or use shell history? Maybe I am doing it wrong.

[asavageiv]

The idea is loosely based on this:
https://github.blog/engineering/scripts-to-rule-them-all/

I use docker devcontainers heavily so I'm often spinning up a clean environment with no shell history.

[pabzm]

how do you all build the containers when doing local dev?

I don't do it often, usually work with the images built in the CI.

Why do you build them locally?

[asavageiv]

I build them locally for faster iteration. Do you make a commit and push to CI before doing any testing or are you editing directly inside of running containers? My flow was:

1. Make edits to the code
2. Build appropriate containers with appropriate tags (sometimes push the image to a remote machine, depending on where I'm doing the editing vs where the containers are running)
3. Stop and start the containers with bypass_container_update/mastercontainer_update
4. Do testing

Sometimes I would make edits directly in the container then copy them back to my source code directory.
I tried out bind-mounting some directories into containers, but permissions got tricky.